[Issue 8774] 2.059 worked 2.060 does not: nested delegate memory corruption

[d-bugmail at puremagic.com]

http://d.puremagic.com/issues/show_bug.cgi?id=8774



--- Comment #25 from Dmitry Olshansky <dmitry.olsh at gmail.com> 2012-12-26 12:41:47 PST ---
(In reply to comment #12)
> Well, we probably should make sure that by the time Thread.start() returns, the
> thread is joinable (waiting for the thread to start in Thread.join() would
> probably be undesirable).
> 
> In any case, it probably isn't a bug, but a very reasonable enhancement request
> - I know I'd expect it to behave like that.

I see no reason to believe it's not the case right now. Basically after
t.start() was called join should always succeed (and wait on the thread to
terminate, potentially blocking indefinetely).

-- 
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
------- You are receiving this mail because: -------