Go Channels Concurrency
The cluster focuses on discussions about Go's channels and goroutines for concurrency, including their philosophy, advantages, limitations, best practices, and comparisons to alternatives like mutexes or other languages' approaches.
Activity Over Time
Top Contributors
Keywords
Sample Comments
Unless I'm mistaken you can already do that with go's channels
sounds alot like the golang channel "phylosophy":)
If channels are the wrong way to do things in Golang, what is the right way?
Channels are not always the best solution (unless you're referring to Rust channels?)https://www.jtolio.com/2016/03/go-channels-are-bad-and-you-s...
Channels require concurrency; you have to spin up another goroutine and take care not to let or deadlock. Channels are for communication between goroutines, not for general abstraction.
Isn't this what channels are for? Doesn't Go have this already built in?
What do you think about goroutines and channels?
Avoid channels except for straight forward, producer-consumer workflows. Use mutexes and other traditional concurrency primitives for other stuff. Channels are a huge shotgun with caveats.
yes, channels and goroutines are a concept that doesn't transfer from C++ or Java :) good job pointing out the exception!
"Or you can use channels, if you need a little more control." that means the guy doesn't even understand the `share memory by communicating` model of go