forcing "@nogc" on class destructors

[Meta via Digitalmars-d]

On Tuesday, 20 January 2015 at 20:25:15 UTC, Meta wrote:
> Is it that subtle of a bug? Your program crashes once, you go 
> on the forums and find the answer, and then you know never to 
> do it again.

Furthermore, this is something that seems like it'd be incredibly 
simple to add to dscanner (of course, everyone doesn't use 
dscanner). Someone who wants to avoid hidden allocations in a 
destructor will mark all their class destructors @nogc anyway, so 
enforcing it seems like it wouldn't add much value over what can 
already be done.