Concurrency architecture for D2

[retard]

Sun, 27 Dec 2009 14:32:52 -0600, Andrei Alexandrescu wrote:

> I think we are now in the position of defining a solid set of
> concurrency primitives for D. This follows many months of mulling over
> models and options.
> 
> It would be great to open the participation to the design as broadly as
> possible, but I think it's realistic to say we won't be able to get
> things done on the newsgroup. When we discuss a topic around here,
> there's plenty of good ideas but also the inevitable bikeshed
> discussions, explanations being asked, explanations being given, and
> other sources of noise. We simply don't have the time to deal with all
> that - the time is short and we only have one shot at this.
> 
> That's why I'm thinking of creating a mailing list or maybe another
> group for this. Any ideas on what would be the best approach? I also
> want to gauge interest from threading experts who'd like to participate.
> Please advise: (a) whether you would like to participate to the design;
> (b) keep discussions on the general group; (c) create a separate
> newsgroup; (d) create a mailing list. The latter would have open
> enrollment.

Have the discussions here ever led to a conclusion and get implemented? 
You should at least disallow posting via the web interface - those broken 
threads start to annoy some people.

While you're at it, I, for one, welcome a new concurrency architecture 
that scales nicely when I want optimal array processing on i486, PII/SSE, 
P4/HT, Core i7/HT/SSE 4.2, and perhaps also on Beowulf (takes care of 
network latencies). Would it use the new immutable actor/message model 
you're building?