forcing "@nogc" on class destructors

[Steven Schveighoffer via Digitalmars-d]

On 1/20/15 4:37 PM, "Ola Fosheim =?UTF-8?B?R3LDuHN0YWQi?= 
<ola.fosheim.grostad+dlang at gmail.com>" 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".

It's neither spurious, nor a race condition.

-Steve