[D-runtime] A mechanism to kill threads

[Sean Kelly]

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.