3 ms·
To expand on this a bit, while they went back to native threading, they didn't ditch any of the type system and library work designed to make message passing co
by sanderjd 12y ago
To expand on this a bit, while they went back to native threading, they didn't ditch any of the type system and library work designed to make message passing convenient and memory safe, which is (arguably) more fundamentally important for concurrency than M:N threading.
- rubiquity 12y agoGreat point. I just meant in the context of the languages I cited Rust doesn't offer similar abstractions.
- sanderjd 12y agoYeah not disagreeing with you at all. It doesn't work the same way "concurrency-focused languages" generally work right now, but it does share the message-passing philosophy with them. Interestingly, I heard a rumor that Go is considering moving to 1:1 threading on Linux, which would align it with Rust's current approach, just without the memory protection capabilities of the type system (though I have no idea whether or not this is true).