assert semantic change proposal

[via Digitalmars-d]

On Wednesday, 6 August 2014 at 21:57:50 UTC, Walter Bright wrote:
> On 8/6/2014 10:18 AM, Sean Kelly wrote:
>> So from a functional perspective, assuming this is a 
>> multithreaded app, what
>> should the procedure be when an AssertError is thrown in some 
>> thread?
>
> Print message, stop the process and all its threads.
>
> Rationale: the program is in an unknown, invalid state, which 
> will include any thread (or process) that has access to memory 
> shared with that failed thread.

Strictly speaking we would need to kill only those threads. But I 
guess it wouldn't be worth the effort, because the remaining 
threads are most likely not expecting them to disappear and 
couldn't recover from this.