Hacker News new | ask | show | jobs
by strictfp 1330 days ago
I would love it if some language would implement a segmented heap, where each part could be GCed separately.

Erlang has this model with it's lightweight processes. And it's a great model that helps not only with GC, but also guaranteeing no shared state between different parts of the code.

2 comments

> where each part could be GCed separately

That would mean disallowing cyclical references across different GC heaps; non-cyclical references would just create additional GC roots. It would be a step away from totally automated memory management and towards something closer to "smart" reference counting.

I'm saying that references between heaps should be disallowed altogether.
See Pony.