Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.programming.threads > #4929 > unrolled thread

About Rust programming language..

Started byHorizon68 <horizon@horizon.com>
First post2019-02-11 13:03 -0800
Last post2019-02-11 13:03 -0800
Articles 1 — 1 participant

Back to article view | Back to comp.programming.threads


Contents

  About Rust programming language.. Horizon68 <horizon@horizon.com> - 2019-02-11 13:03 -0800

#4929 — About Rust programming language..

FromHorizon68 <horizon@horizon.com>
Date2019-02-11 13:03 -0800
SubjectAbout Rust programming language..
Message-ID<q3snvi$rhu$5@dont-email.me>
Hello..


About Rust programming language..

I have just read the following about Rust programming language:

"What I’m going to discuss here is the choice made in Rust to disallow 
having multiple mutable aliases to the same data (or a mutable alias 
when there are active immutable aliases), even from the same thread.
This is essentially the “Read-Write lock” (RWLock) pattern, except it’s 
not being used in a threaded context, and the “locks” are done via 
static analysis (compile time “borrow checking”)."

Read more here:

https://manishearth.github.io/blog/2015/05/17/the-problem-with-shared-mutability/

So as you are noticing that to avoid race conditions etc. Rust is
using the Read-Write lock (RWLock) pattern , but i think this is not a 
fine-grained parallelism, so with the Read-Write lock (RWLock) pattern
of Rust you are loosing fine-grained parallelism that gives
much more parallelism.


Thank you,
Amine Moulay Ramdane.

[toc] | [standalone]


Back to top | Article view | comp.programming.threads


csiph-web