RFC: moving forward with @nogc Phobos

[Andrei Alexandrescu via Digitalmars-d]

On 9/30/14, 12:10 PM, "Marc Schütz" <schuetzm at gmx.net>" wrote:
> I would argue that GC is at its core _only_ a memory management
> strategy. It just so happens that the one in D's runtime also comes with
> an allocator, with which it is tightly integrated. In theory, a GC can
> work with any (and multiple) allocators, and you could of course also
> call GC.free() manually, because, as you say, management and allocation
> are entirely distinct topics.

I'm not very sure. A GC might need to interoperate closely with the 
allocator. -- Andrei