On 05/26/2010 09:47 PM, BLS wrote:
On 26/05/2010 23:59, Steven Schveighoffer wrote:
I don't think it will be analogous to a Tango/Phobos separation.
Dcollections supports ranges, and the major interface to Andrei's
containers is ranges, and if my implementations are accepted, both
will probably even be using the same underlying implementations. So I
think the two libs will quite happily exist together. I am
disappointed that dcollections wasn't chosen, but given the eventual
API that Andrei has come up with, I think it didn't really have a shot
from the beginning.
I have not yet seen a statement regarding the replacement (hopefully hot
swapped) feature of underlaying data structures
dCollections has support, std.collection... dunno
In case that Andrei decides to ignore that feature I can't see how
Dcollections and std.collection will harmonize.
It's even better than that, but you need to look at things a bit
differently.
std.container will not contain hot-swappable components. It will contain
components that could be used in some of the hot swaps. It's just one
level lower than what you are discussing.
That doesn't make it any more or less incompatible with dcollections.
Andrei
