forcing "@nogc" on class destructors

[via Digitalmars-d]

On Thursday, 22 January 2015 at 14:07:31 UTC, Steven 
Schveighoffer wrote:
> resources) and everything works fine. And the runtime catches 
> any slips with an appropriate handling (abort instead of 
> corrupt memory).

Runtime errors that could have been a compile time error should 
always be caught at compile time. Spurious runtime errors are 
just as bad as null pointer accesses.