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 dilap on Wednesday July 08, 2015 @11:52PM (#9856063)
This works for erlang 'cuz it's functional. Not gunna work for something like Go.

Something like ARC would work for Go though (right?), & I agree it's a really nice approach, and I don't really get why it's not more widely used.

[ Parent | on HN ]
Re:Go GC: Solving the Latency Problem in Go 1.5 by vezzy-fnord on Thursday July 09, 2015 @12:04AM (#9856086)
It works for Erlang because of its process model. I don't think it has anything to do with it being functional.
[ Parent | on HN ]
Re:Go GC: Solving the Latency Problem in Go 1.5 by dilap on Thursday July 09, 2015 @12:48AM (#9856196)
Yup, you're right. I just meant that to have a program composed of many processes that can be stopped & collected independently, those processes have to communicate 'functionally', i.e., without shared mutable memory. (So this isn't a viable approach for languages like Go where all the goroutines share memory.)
[ Parent | on HN ]
Re:Go GC: Solving the Latency Problem in Go 1.5 by masklinn on Thursday July 09, 2015 @03:40AM (#9856628)
> So this isn't a viable approach for languages like Go where all the goroutines share memory.

Something Go has been criticised for since it was originally unveiled back in 2009.

[ Parent | on HN ]
Re:Go GC: Solving the Latency Problem in Go 1.5 by chaotic-good on Thursday July 09, 2015 @03:46AM (#9856645)
In erlang old data structures can't reference new data. This simplifies GC a lot.
[ Parent | on HN ]
Re:Go GC: Solving the Latency Problem in Go 1.5 by vezzy-fnord on Thursday July 09, 2015 @09:37AM (#9857753)
Immutability is orthogonal to FP as a whole.
[ Parent | on HN ]