std.experimental.allocator and @nogc

[Hildigard Sandyman via Digitalmars-d]

On Monday, 9 May 2016 at 06:35:36 UTC, rikki cattermole wrote:
> On 09/05/2016 6:22 PM, Hildigard Sandyman wrote:
>> It's true but... why do you bother with IAllocator ? 
>> Everything can be
>> set a compile time with a template parameter. As long as the 
>> param is a
>> struct with allocate/deallocate/reallocate it's OK. you can 
>> use already
>> a good part of the package content in a @nogc fashion.
>>
>> Do you have an example where IAllocator must be used and 
>> where, for
>> example, Mallocator can't be passed ?!
>
> The moment where you need to use OOP, you most definitely need 
> IAllocator.
> I cannot make a windowing library without the use of IAllocator.
>
> You can't always template functions with the type that is the 
> allocator.
> Its just not possible or reasonable.

Yes there's a problem with this but that doesn't mean that whole 
package is concerned. The first message clearly orientates the 
answer:

> It seems to me, that std.experimental.allocator should work 
> with @nogc
It should == It doesn't yet

> Are there plans for this ?
Question is based on the previous wrong assumption, but since the 
most important part of the message is the Q itself, it makes 
people swallow the craps.

So basically anyone not well informed who reads this can deduce 
that it doesn't work at all.