std.allocator needs your help

[Brad Roberts]

On 9/22/13 7:28 PM, Andrei Alexandrescu wrote:
> On 9/22/13 6:35 PM, Manu wrote:
>
>> Are you intending to be able to associate a particular allocator with a
>> class declaration?
>
> No, or at least not at this level.
>
>> What about a struct declaration?
>
> Same answer.
>
>> What about a region of code (ie, a call tree/branch).
>> What if the given allocator should be used for most of the tree, except
>> for a couple of things beneath that always want to use their explicit
>> allocator?
>
> The proposed design makes it easy to create allocator objects. How they are used and combined is
> left to the application.

I think the question he's asking, which a lot of people are anxiously anticipating is... how does 
the intersect with the parts of the language and core libraries that have been blocked (for a loose 
definition of blocked) waiting for the allocator design.  Primarily, but far from exclusively, the 
container library.

Yes, the allocator design is clearly a lower level component, but it's also far easier than the 
integration with the language and libraries.