3 ms·
No mention of a generational collector. The word concurrent is in there though.
by kristianp 12y ago
No mention of a generational collector. The word concurrent is in there though.
- Zariel 12y agoIn 1.3 the GC is concurrent mark and sweep
- taeric 12y agoI thought generational and mark/sweep were orthogonal. That is, can't generational still be mark and sweep? You just don't mark and sweep the entire reference set?
- jlouis 12y agoGenerational collectors can pick any strategy for each of their generations. What to pick depends on language, and what characteristics you want to get easily.
- stcredzero 12y agoRecounting for tenured generations would be awesome!
- thescrewdriver 12y agoWhy mod someone down for asking about a generational GC?
- kristianp 12y agoMy comment was a little flip, I know, I should have asked a more friendly question. I'm wondering why it hasn't been discussed (as far as I can tell). Java has had it for ages, Ruby will have it in 2.1 and Python appears to have it as well [1]. Isn't Generational GC feasible in Go for some reason? [1] https://docs.python.org/2/library/gc.html https://docs.python.org/2/library/gc.html Edit: Here is a discussion of gc in go. Go has only just gotten a precise collector, which is a requirement of a generational gc, to allow moving pointers. https://groups.google.com/forum/#!topic/golang-nuts/fiOs3mGH1es https://groups.google.com/forum/#!topic/golang-nuts/fiOs3mGH...
- jeltz 12y agoFYI: Ruby 2.1 has been released for some time now.
- logicchains 12y agoI've heard talk of plans for a generational, moving GC in future. It's just not something that can be implemented overnight, especially in a language with internal pointers (which Java, Ruby and Python lack).