You don't have to use mutex ! The Rust type system has two traits to ensure thread-safety : Send and Sync, and you can safely use anything which implement those traits. Mutex is one easy way to have these capabilities, but it's not the only one. You can build your own thread-safe data structure if you want, or even use third-party ones like crossbeam[1]. The compiler will then ensure that you never use non-thread-safe objects accross threads.
> At least parrot and pony do away without that nonsense.
What is parrot ? I've read about pony but not parrot, and Google isn't helping.
[1] : https://github.com/crossbeam-rs/crossbeam/blob/master/README...
Please don't include these sorts of things in comments. They're worse than unnecessary: they take us further away from the kinds of thoughtful, civil discussions we're after.
What specifically do people not have an idea about?
> So why do have to manually mutex or semaphore your threads?
You don't _have_ to, but it is an option. Rust, as a low-level language, provides a number of options for dealing with concurrency. Frankly, I wrote that chapter above and in a hurry; it's my least favorite out of the whole book.
Rust can prove a lack of data-races at compile time, which is a big deal.
But like Rust it needs mutexes and errors with wrong or missing mutexes. So in this regard it's equal to Rust.