News for hackers. Stuff that matters.
Re:Rust concurrency: the archetype of a message-passing bug by justinpombrio on Monday June 22, 2020 @11:35AM (#23601359)
> Outlawing concurrent shared state means that every communication between two threads needs to be formatted as a "message" in whatever abstraction is in use.

> It's a real requirement, and Rust has little to say about it in its standard library

So, I don't know much about concurrency, but you're looking for like, a Mutex, right? They're in the standard library and used all the time.

https://doc.rust-lang.org/stable/std/sync/struct.Mutex.html

And RwLock, a variant on Mutex that allows either one writer or multiple concurrent readers:

https://doc.rust-lang.org/stable/std/sync/struct.RwLock.html

Re:Rust concurrency: the archetype of a message-passing bug by lubesGordi on Monday June 22, 2020 @01:11PM (#23602740)
Yes! There's nothing weird about rust's synchronization on shared state. If you have a mutex, you can do what you want just like in c++. The mpsc::channel thing that gpp might be talking about is just a nice to have tool for sending data between threads. No one is forcing its use.