One awesome GC feature we will use in Mir!

[Per Nordlöw]

On Tuesday, 18 September 2018 at 14:23:44 UTC, 9il wrote:
> I just remember that D's GC has NO_SCAN [1] attribute!

I thought D libraries like Mir and Lubeck only had to care about 
when to call GC.addRange after allocations that contain pointers 
to GC-backed storage and GC.removeRange before their 
corresponding deallocations. But that's perhaps only when using 
non-GC-backed allocators (not using new), right?