> Go has value types and doesn't suffer from this issue, which is a reason why having a generational GC is not that important for Go.
Go is in the same camp as C#/.NET here, where the generational hypothesis certainly holds and therefore .NET uses a generational garbage collector. I am certain that the generational hypothesis holds for Go as well.
Not having a generational GC is a design mistake in Go. Google should fix that.
Go is in the same camp as C#/.NET here, where the generational hypothesis certainly holds and therefore .NET uses a generational garbage collector. I am certain that the generational hypothesis holds for Go as well.
Not having a generational GC is a design mistake in Go. Google should fix that.