3 ms·
I'm not sure how the current implementation of Go handles it, but its spiritual relatives Modula-3/Oberon handled this quite well, with a GC for most occasions
by mhd 11y ago
I'm not sure how the current implementation of Go handles it, but its spiritual relatives Modula-3/Oberon handled this quite well, with a GC for most occasions and ways to bypass this with "unsafe" modules that allowed for untracked allocations/deallocations and pointer arithmetic. It's not really an either/or situation by (language) definition...
- pjmlp 11y agoYes, it is quite sad that the massive industry adoption of Java and .NET forced those languages into extinction. Although from all mainstream languages, C# is probably the closest in spirit to Modula-3.
- stcredzero 11y agoI'm puzzled as to why all mature GC doesn't have "permspace."
- schmichael 11y agoGo's GC is non-moving and therefore cannot be generational. http://llvm.cc/t/go-1-4-garbage-collection-plan-and-roadmap-golang-org/33 http://llvm.cc/t/go-1-4-garbage-collection-plan-and-roadmap-...
- pcwalton 11y agoNitpick: you don't need moving GC for generational GC. But you lose most (but not all) of the benefit of generational GC without moving GC.