4 ms·
Not that I don't believe, but can you provide a citation for that fact about Rust in parallel mode? I don't follow Rust too closely, but I hadn't heard of that.
by eatonphil 12y ago
Not that I don't believe, but can you provide a citation for that fact about Rust in parallel mode? I don't follow Rust too closely, but I hadn't heard of that. That is really interesting.
- deleted 12y ago[deleted]
- zokier 12y agoRust documentation on concurrency and shared mutable state might help: http://doc.rust-lang.org/book/concurrency.html#safe-shared-mutable-state http://doc.rust-lang.org/book/concurrency.html#safe-shared-m... and http://doc.rust-lang.org/nightly/intro.html#concurrency http://doc.rust-lang.org/nightly/intro.html#concurrency
- nercury 12y agoInteresting read would be here: http://doc.rust-lang.org/std/thread/ http://doc.rust-lang.org/std/thread/ It is also guaranteed by ownership system: in the safe mode (which is default) rust will statically (at compile time) ensures that a value can only be mutated at a single execution point. It is done by moving, instead of copying any value _by default_, unless it is wrapped in some kind of synchronization primitive or implements a _Copy_ trait. Synchronization primitives themselves are implemented in unsafe mode, thus limiting the unsafe code scope and allowing custom unsafe code which can also be wrapped in safe interface.