[D-runtime] A mechanism to kill threads

[Alex Rønne Petersen]

It's the user's responsibility, just as with any of the other 'unsafe'
functions. Also, it's the runtime, not the standard library. I think
there is a significant difference between those two terms. You
shouldn't touch the runtime in general unless you're prepared to go
low-level.

Regards,
Alex

On Wed, May 16, 2012 at 11:48 PM, Sean Kelly <sean at invisibleduck.org> wrote:
> On May 16, 2012, at 2:39 PM, Alex Rønne Petersen wrote:
>
>> What do you mean? This might hold true if you're executing in a signal
>> handler, but if the code you execute after suspending/killing a bunch
>> of threads does not touch any state that the suspended/killed threads
>> owned/accessed, you'll be fine.
>
> But how do you know what the threads own or are accessing?  This is the standard library.  The user could be doing absolutely anything.
> _______________________________________________
> D-runtime mailing list
> D-runtime at puremagic.com
> http://lists.puremagic.com/mailman/listinfo/d-runtime