Non-freeing GC memory management

Kagamin via Digitalmars-d digitalmars-d at puremagic.com
Wed Nov 18 01:00:21 PST 2015


On Wednesday, 18 November 2015 at 05:49:00 UTC, tcak wrote:
> If this is so, this behaviour of GC encourages to call destroy 
> (or was it clear?) on objects manually to manage the memory 
> more efficiently.

It only runs the destructor, it doesn't free memory.


More information about the Digitalmars-d mailing list