News for hackers. Stuff that matters.
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.)
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.