RFC: moving forward with @nogc Phobos

[Andrei Alexandrescu via Digitalmars-d]

On 10/1/14, 10:25 AM, Oren T wrote:
> The idea is that the unique property is very short-lived: the caller
> immediately assigns it to a pointer of the appropriate policy: either RC
> or GC. This keeps the callee agnostic of the chosen policy and does not
> require templating multiple versions of the code. The allocator
> configured for the thread must match the generated code at the call site
> i.e. if the caller uses RC pointers the allocator must allocate space
> for the reference counter (at negative offset to keep compatibility).

This all... looks arcane. I'm not sure how it can even made to work if 
user code just uses "auto". -- Andrei