forcing "@nogc" on class destructors

[deadalnix via Digitalmars-d]

On Tuesday, 20 January 2015 at 21:37:56 UTC, Ola Fosheim Grøstad 
wrote:
> On Tuesday, 20 January 2015 at 21:29:40 UTC, Steven 
> Schveighoffer wrote:
>> How's that? The current runtime aborts on memory allocation 
>> inside the GC collection routine, it's not a memory safety 
>> issue.
>
> Spurious race conditions in memory deallocation patterns that 
> remain undetected and cause random crashes after deployment are 
> ok? That is not memory safety, it is "memory safety".
>
> The language should prevent this.

That is GC implementation issue, not a language issue. If it 
ain't broken, don't fix it.