News for hackers. Stuff that matters.

A comment on Proposed New Go GC: Transaction-Oriented Collector. Parent comment

Re:Proposed New Go GC: Transaction-Oriented Collector by grandinj on Friday June 24, 2016 @03:40PM (#11972802)
plus Go has now acquired a culture of heavily optimising their code to "not allocate", so allocation is less of an issue for them than runtimes like Java.
[ Parent | on HN ]
Re:Proposed New Go GC: Transaction-Oriented Collector by mtanski on Saturday June 25, 2016 @12:48AM (#11975276)
It's not that those libraries "not allocate" but they work with stack allocation / provided buffers. You can reuse the provided buffers / output objects ... But a lot of req/resp code doesn't so it's just pushing the cost higher up the stack (app vs libraries). Which it self is a good argument for "transactional" GC.
[ Parent | on HN ]