Thought on limiting scope of GC

[Paulo Pinto]

On Friday, 14 February 2014 at 04:41:43 UTC, Jerry wrote:
> Hi all,
>
> I just had the following thought on limiting the gc in regions.
>  I don't
> know if this would address some of Manu's concerns, but here 
> goes:
>
> My thought is to have something like the following:
>
> GC.track();
> auto obj = allocateStuff();
> GC.cleanup(obj);
>
> The idea here is that track() tells GC to explicitly track all 
> objects
> created from that point until the cleanup call.  The cleanup() 
> call
> tells gc to limit its collection to those objects allocated 
> since the
> track() call.  The obj parameter tells gc to consider obj live.
>
> This way, you can avoid tracking everything that may get 
> created, but
> you can limit how much work gets done.
>
> Comments? Slams?
>
> Jerry

How do imagine it to work in multi-core programs? Does it only 
track thread local allocations?