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.)
> 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.
In erlang old data structures can't reference new data. This simplifies GC a lot.