review of std.parallelism

[Andrei Alexandrescu]

On 03/19/2011 04:25 PM, dsimcha wrote:
> On 3/19/2011 4:35 PM, Andrei Alexandrescu wrote:
>> I know you'd have no problem finding the right voice in this discussion
>> if you only frame it in the right light. Again, people are trying to
>> help (however awkwardly) and in no way is that ridiculous.
>
> Fair enough. Now that I think of it most of my frustration is that these
> details are only getting looked at now, when I have a week (and an
> otherwise very busy week) to fix all this stuff, when this module has
> been officially in review for the past two weeks and unofficially for
> several months. I would be much more open to this process if the issues
> raised could be fixed at my leisure rather than on a hard and tight
> deadline. This is exacerbated by the fact that I have another important,
> unrelated deadline, also next Friday.
>
> At the same time, though, I'm afraid that if we didn't fix a vote date
> and put some urgency into things, the pace of the reviews would be
> glacial at best, like it was for the first two weeks of official review
> and the months of unofficial review.

Exactly. I understand. Well here's a suggestion. How about we "git 
stash" this review? I recall another submission was vying for the queue 
so we can proceed with that while you have time to operate the changes 
you want. If not, we can simply wait 2-3 weeks and then have you 
resubmit for a shorter process (1-2 weeks) that would gather more 
feedback (hopefully minor that time) and votes.

Lars?

> Also increasing the deadline pressure issue, Michael Fortin just caused
> me to rethink the issue of exception handling in parallel foreach. I had
> more-or-less working code for this, but I realized it's severely broken
> in subtle ways that I've (knock on wood) never actually run into in real
> world code. It's gonna take some time to fix. These kinds of issues with
> error handling code can very easily slip under the radar in a library
> with only a few users, and unfortunately, one has. I definitely know how
> to fix it, but I have to implement the fix and it's somewhat
> non-trivial, i.e. I'm debugging it now and it's looking like a marathon
> debugging session.

Fixing these sooner rather than later would be great, so  all the better 
for suspending the review.

Andrei