Reference count, don't garbage collect

Re:Reference count, don't garbage collect by eru on Friday July 29, 2022 @10:22PM (#32283743)

There are solutions to this one. Real time garbage collectors are a thing. You just might not be able to collect the cycle in one GC run.

Or you can do what Erlang does: Erlang has neither mutation nor laziness, so you can't create cycles. The GC also lays out object in topological order in memory, so that you can detect garbage without tracing every life object.

[ Parent | on HN ]

Re:Reference count, don't garbage collect by viraptor on Saturday July 30, 2022 @12:01AM (#32284176)

The comment claimed "There are zero GC pauses." Tbh, it's not clear how to interpret that. But real time simply means the pauses are guaranteed not to cross the realtime response budget. You still need to schedule the collection while the mutator is paused.

[ Parent | on HN ]

Re:Reference count, don't garbage collect by omginternets on Friday July 29, 2022 @11:52PM (#32284134)

Where can I read about Erlang’s magic?

[ Parent | on HN ]

Re:Reference count, don't garbage collect by eru on Saturday July 30, 2022 @12:10AM (#32284211)

Google suggests https://stackoverflow.com/questions/10221907/garbage-collect...

[ Parent | on HN ]