Re: is it safe to call `GC.removeRange` in dtor?

[ketmar via Digitalmars-d-learn]

thank you both. then i think that it should be explicitly stated 
in core.memory.

Re: is it safe to call `GC.removeRange` in dtor?

[Steven Schveighoffer via Digitalmars-d-learn]

On 6/27/15 5:53 PM, ketmar wrote:

is it safe to call `GC.removeRange` in dtor? i believe it should be safe,
so one can perform various cleanups, but documentation says nothing about
guarantees.


Hm... I can't see any reason why it wouldn't be allowed. removeRange 
shouldn't allocate, so the one forbidden thing is not used.


And removing a range, by definition, means it's not being collected. So 
you can be assured that the data still exists.


I'm not 100% sure, though.

-Steve

Re: is it safe to call `GC.removeRange` in dtor?

[rsw0x via Digitalmars-d-learn]

On Saturday, 27 June 2015 at 21:53:33 UTC, ketmar wrote:
is it safe to call `GC.removeRange` in dtor? i believe it 
should be safe, so one can perform various cleanups, but 
documentation says nothing about guarantees


It's not documented. Afaik parts of the standard library depend 
on this behavior so I'd say ok* where the asterisk means submit 
a specification update.