On Thursday, 10 July 2014 at 10:43:39 UTC, Dicebot wrote:
On Thursday, 10 July 2014 at 03:59:15 UTC, logicchains wrote:
Actually, an important question that should be considered:
does D want actor-style concurrency, like Erlang and Akka, or
CSP-style concurrency, like Rust, Go and Haskell? Or both?
Deciding this would allow efforts to be more focused.
AFAICS D already has actor-style concurrency with vibe.d
extensions for std.concurrency so this is an easy choice ;)
Are there any tutorials or blog posts out there demonstrating how
to use this? I think posts along the lines of "This is a
CSP/message passing program in Go/Erlang. This is the same
program translated into D; look how concise and faster it is!"
could attract a lot of interest.
Reading the code in the pull request [1], for instance, makes me
wonder how to tell if `spawn()` is spawning a thread or a fibre.
Can a tid refer to a fibre? If so, why's it called a thread ID,
and how do I tell if a particular tid refers to a thread or
fibre? It would be great to have these kinds of questions
answered in an easily available reference (for instance, the
documentation for std.concurrency, which currently doesn't even
mention fibres or vibe.d).
1. https://github.com/D-Programming-Language/phobos/pull/1910
