DIP60: @nogc attribute

Timon Gehr via Digitalmars-d digitalmars-d at puremagic.com
Thu Apr 17 07:37:27 PDT 2014


On 04/17/2014 02:34 PM, Manu via Digitalmars-d wrote:
> On 17 April 2014 21:57, John Colvin via Digitalmars-d
> <digitalmars-d at puremagic.com <mailto:digitalmars-d at puremagic.com>> wrote:
>
>     On Thursday, 17 April 2014 at 11:31:52 UTC, Manu via Digitalmars-d
>     wrote:
>
>         ARC offers a solution that is usable by all parties.
> ...
> You can't use a GC in a
> low-memory environment, no matter how it's designed. It allocates until
> it can't, then spends a large amount of time re-capturing unreferenced
> memory. As free memory decreases, this becomes more and more frequent.

What John was trying to get at is that the two quoted statements above 
are in contradiction with each other. An GC is a subsystem that 
automatically frees dead memory. (Dead as in it will not be accessed 
again, which is a weaker notion than it being unreferenced.)

Maybe the distinction you want to make is between ARC and tracing 
garbage collectors.



More information about the Digitalmars-d mailing list