std.allocator ready for some abuse

[bitwise via Digitalmars-d]

On Saturday, 12 September 2015 at 06:30:42 UTC, bitwise wrote:
> On Saturday, 12 September 2015 at 00:31:27 UTC, Andrei 
> Alexandrescu wrote:
>> [...]
>
> This sounds like the default setup I'll be using. The 
> containers will use a Mallocator by default, so I will have to 
> add the ranges when the contained type is found to have 
> indirections.
>
> [...]

Alternatively, GC.addRange() could return a value indicating 
whether or not the range had actually been added(for the first 
time) and should be removed.

    Bit