2 ms·
> Will they do CSP AND actors (they're different!)? Will there be some kind of OpenMP type thing? Rust builds support for all of these models based on it's bas
by zozbot234 3y ago
> Will they do CSP AND actors (they're different!)? Will there be some kind of OpenMP type thing?
Rust builds support for all of these models based on it's basic underlying "shared ^ mutable" and "Send/Sync" safety guarantees. It should be quite clear based on this whether you're sharing access to some read-only data, staying within a single-threaded context with mutability, or relying on some sort of synchronization primitive (be it atomic data, locks, r/w mutexes etc). The fact that we understand some uses of these facilities as involving patterns such as "CSP" or "Actors" is quite beside the point.
- camgunz 3y agoI don't super understand your point. I understood TFA to making the argument that dealing with the low-level business of stuff like mutexes and async/await isn't what most people want to do: > We should aspire not to simplify the system by hiding the differences between futures and threads, but instead to find the right set of APIs and language features that build on the affordances of futures to make more kinds of engineering achievable than before. The stuff you listed, along with async/await, makes this possible. Isn't that what TFA is saying?