Processes and Channels, cf. goroutines.

[Bienlein]

On Thursday, 6 February 2014 at 13:00:51 UTC, logicchains wrote:

> Note that the Go race detector isn't a static analysis tool 
> that identifies deadlocks at compile time; it instruments the 
> code and then detects race conditions at runtime. It's based on 
> the C/C++ ThreadSanitizer runtime library, so a similar thing 
> could probably be implemented for D.

Thanks for pointing out. I seem to have interpreted the 
information I had to optimistically.

> Rust is actually moving away from directly tying the language 
> to one kind of threading, so that it's possible to choose 
> between M:N threading (goroutines) or 1:1 threading (system 
> threads). See this discussion: 
> https://mail.mozilla.org/pipermail/rust-dev/2013-November/006550.html 
> for the reasoning behind this.

Yes, I read an interview on infoq.com saying the same thing which 
confused me a bit. M:N threading is still there, but is there 
still some focus on it as with the Go people ? Anyway, as long as 
D continues its own way with fibers ... ;-).