[swift-evolution] What're the Swift team's thoughts on Go's concurrency?
spestov at apple.com
Wed Aug 10 16:48:53 CDT 2016
As I understand it, a big weakness of Go's model is that it does not actually prevent data races. There's nothing preventing you from sharing pointers to mutable values between tasks, but I could be wrong about this.
> On Aug 9, 2016, at 12:04 PM, Dan Stenmark via swift-evolution <swift-evolution at swift.org> wrote:
> I'd like to inquire as to what the Swift team thoughts on Go's concurrency model are? I'm not referring to convenience of the 'go' keyword and nor am I referring to how the language handles Channels, both of which being what most folks associate with it. Rather, I'd like to ask about the language's use of Green Threads and how the runtime handles the heavy lifting of multiplexing and scheduling them. What are some of the strengths and weaknesses the Swift team sees to Go's approach?
> (DISCLAIMER: I'm posting this for academic reasons, not as a pitch. While the Swift team's responses may inform opinions on the matter, I do not want this to turn into a 'this is how I think Swift should do concurrency' debate. That discussion will come when it comes.)
> swift-evolution mailing list
> swift-evolution at swift.org
More information about the swift-evolution