News for hackers. Stuff that matters.

A comment on Go GC: Solving the Latency Problem in Go 1.5. Parent comment

Re:Go GC: Solving the Latency Problem in Go 1.5 by mseepgood on Thursday July 09, 2015 @02:20AM (#9856415)
The "A" in ARC is a bit of an euphemism. You basically move the coding of your memory management into the type signatures, which don't write themselves automatically either. The amout of thoughts you have to make during development is the same.
[ Parent | on HN ]
Re:Go GC: Solving the Latency Problem in Go 1.5 by andrewchambers on Thursday July 09, 2015 @05:59AM (#9857008)
I thought the A was for atomic, ARC is atomic reference count. RC is non atomic.
[ Parent | on HN ]
Re:Go GC: Solving the Latency Problem in Go 1.5 by mseepgood on Thursday July 09, 2015 @06:54AM (#9857153)
https://en.wikipedia.org/wiki/Automatic_Reference_Counting
[ Parent | on HN ]
Re:Go GC: Solving the Latency Problem in Go 1.5 by andrewchambers on Thursday July 09, 2015 @07:03AM (#9857176)
My mistake, in rust it is atomic, in objective c it is automatic.
[ Parent | on HN ]