News for hackers. Stuff that matters.
Re:Updating the Go Memory Model by tene on Monday July 12, 2021 @08:35PM (#27816616)
This kind of trouble is exactly why Rust's channels feel much more intuitive to me than Go's.

With channels in Rust, the channel is closed when either all senders or all receivers are dropped. This means that doing the default obvious thing is also correct, for a much larger set of tasks than made easy by Go's API choices, and it stays correct under refactoring.

There are no comments on this comment yet.