3 ms·
> Channels pass ownership of allocated objects, they don't perform copies or allocations themselves (once you've allocated the channel and the objects you want
by eternalban 9y ago
> Channels pass ownership of allocated objects, they don't perform copies or allocations themselves (once you've allocated the channel and the objects you want to pass).
And? Did I say they did?
> I don't think the article says anything about concurrent allocations
No it doesn't. Point was that it is not a general purpose approach. GCs are.
- dullgiulio 9y agoI've just searched for the word "channel" in the article: zero results. The "original mantra" is "Channels orchestrate, locks serialize" and hasn't been dropped by anyone.
- eternalban 9y ago2010: https://blog.golang.org/share-memory-by-communicating https://blog.golang.org/share-memory-by-communicating There is nothing wrong with that approach. It does put a ceiling on performance, however.