Simpler and faster GC for Go

Re:Simpler and faster GC for Go by thescrewdriver on Thursday July 17, 2014 @11:43AM (#8048136)

Why mod someone down for asking about a generational GC?

[ Parent | on HN ]

Re:Simpler and faster GC for Go by kristianp on Thursday July 17, 2014 @07:50PM (#8050911)

My 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

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/fiOs3mGH...

[ Parent | on HN ]

Re:Simpler and faster GC for Go by logicchains on Friday July 18, 2014 @12:04AM (#8051603)

I'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).

[ Parent | on HN ]

Re:Simpler and faster GC for Go by jeltz on Thursday July 17, 2014 @09:06PM (#8051166)

FYI: Ruby 2.1 has been released for some time now.

[ Parent | on HN ]