[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [GNUnet-developers] [GSoC] Question on "Rust implementation of GNUne

From: Christian Grothoff
Subject: Re: [GNUnet-developers] [GSoC] Question on "Rust implementation of GNUnet utils" project
Date: Mon, 21 Mar 2016 20:45:12 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Icedove/38.6.0

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.


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>>. 

Attachment: signature.asc
Description: OpenPGP digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]