forcing "@nogc" on class destructors

[Steven Schveighoffer via Digitalmars-d]

On 1/20/15 4:39 PM, ketmar via Digitalmars-d wrote:
> On Tue, 20 Jan 2015 16:30:14 -0500
> Steven Schveighoffer via Digitalmars-d <digitalmars-d at puremagic.com>
> wrote:
>
>> On 1/20/15 4:06 PM, ketmar via Digitalmars-d wrote:
>>> On Tue, 20 Jan 2015 15:51:17 -0500
>>> Steven Schveighoffer via Digitalmars-d <digitalmars-d at puremagic.com>
>>> wrote:
>>>
>>> p.s. another point is that all mechanics compiler needs for doing such
>>> checks is already there, so it's not a huge change to compiler
>>> codebase. it's not something that requires adding a whole new analysis
>>> code.
>>>
>>
>> You can always put @nogc on the dtor if you want.
> seems that you completely missing my point. (sigh)
>

Nope, not missing it. The mechanics are there. You just have to annotate.

What's the first thing you do if you aren't sure your destructors are 
running?

~this() { writeln("in dtor"); }

oops, sorry, can't do that, it's @nogc! I don't think this is a tenable 
situation.

-Steve