Jason House wrote:
Andrei Alexandrescu Wrote:
But let's not forget we have concurrency ahead of us. I encourage you
all to chime in with your thoughts and ideas regarding all aspects of
concurrency. The recent multicore performance bug is a great starting
point. If you try e.g. shared and it's broken, let us know. If you try
it and it works, push it til it breaks. If you have ideas on how to make
semantic checking better, pipe up.
I posted several shared issues to the NG a few days ago and got no replies.
Most of it was about poor error messages (both misleading text and missing
file/line numbers). I should do proper bugzilla entries but haven't tinkered
with D much since. As always, this post comes from my phone instead of a proper
computer, or else I'd provide a link or do the bugzilla entries while I'm
thinking of it.
IIRC, the most troublesome error happened when I created "shared this(){...}" constructor and no information on where it caused errors.
Thanks, Jason. I did see those messages but I didn't want to dilute
focus back when you posted them.
If you could put together bugzilla entries as you try things, that would
be great. The shared constructor I'll experiment with first.
Andrei
