Addendum: this is another key point why we got rid of pthread's in GNUnet C, as deadlocks in a large code base can get both really nasty to avoid or find/resolve. So whatever you do on Rust, please use concurrency constructions that are deadlock-free. For example, a reasonable subset of X10's concurrency abstractions (async, finish, clocks, no 'when') is deadlock-free. So if you find threads are absolutely necessary (I tend to believe they are not), still make sure you enforce deadlock-freedom by choice of concurrency primitives.
Refs: http://grothoff.org/christian/x10.pdf http://www.eecs.berkeley.edu/~bonachea/upc/x10-spaa07.pdf On 03/21/2016 07:46 PM, Jeff Burdges wrote: > Rust only really provides memory safety, not say protection from > deadlocks due to an incorrect usage of Arc<Mutex<T>>.
signature.asc
Description: OpenPGP digital signature
_______________________________________________ GNUnet-developers mailing list [email protected] https://lists.gnu.org/mailman/listinfo/gnunet-developers
