std.container: fork in the road

[Mike Parker via Digitalmars-d]

On 6/17/2015 3:08 PM, Andrei Alexandrescu wrote:

>
> Regarding compatibility, I see three possibilities:
>
> 1. Just keep the current spec and deal with it. Some containers are and
> will remain garbage collected because they started as such. Add new
> containers that are better alongside them.
>
> 2. Do break compatibility of containers, mainly by taking advantage of
> them being under-documented. In a way we wouldn't break much because not
> much has been specified. There are, however, parts where we'd need to
> change specification.
>
> 3. Leave std.container alone and move forward with
> std.experimental.collection. I am confident the language and its
> endorsed idioms have reached enough maturity to not make this addition
> into a regular event.

My vote goes for 2. I've always understood std.container to be 
incomplete anyway, waiting for the day that std.allocator is ready.