dcollections 1.0 and 2.0a beta released

[Steven Schveighoffer]

Andrei Alexandrescu Wrote:

> On 05/19/2010 11:09 AM, Steven Schveighoffer wrote:
> > After much work and toil, I have created dcollections for D2.
> 
> Awesome! I'm looking through it, unfortunately after wandering in the 
> trunk for a while (I was like, wait, what?). But that was after all good 
> because I saw a lot of awesome improvements in the new library. This is 
> solid work.

Yeah, I will move the D1 version to a branch and copy the D2 to trunk when I get a chance, Part of the reason is the automatic doc generator will puke if the trunk is D2.

> That being said, I think dcollections2 has not yet solved a number of 
> problems, some minor, some annoying, and some fundamental. This makes 
> things quite unpleasant because, willingly or not, I'm in a three-way 
> conflict of interest: (1) I can influence to some extent the decision of 
> adopting dcollections2 for phobos; (2) I have my own design in mind 
> which is competing with dcollections2; (3) my time is scarce so I'm 
> having difficulty executing on that design, whereas dcollections2 is 
> already usable.
> 
> I'm not sure where this leaves us. I'm tempted to post a list of 
> "grievances" with the current design, but it's difficult to make that 
> sound sincere due to the conflict of interest. Let me start by asking 
> this: on a scale of 0 ("no change") to 10 ("redesign the whole thing"), 
> where do you stand regarding the perspective of operating changes to 
> dcollections2?

It depends on what you want to change.  If you say cursors have to go, then I would say no.  If you think some functions/classes need to be renamed, or the module structure needs to be changed, I'd say fine.  

There are other design decisions that can be changed, but I look at it from the perspective of usefulness to me :)  If it stops being useful to me, or does not provide a feature I want, then I'll not use it, and then I won't want to maintain it.

I guess start with the big ones, 'cause minor ones aren't likely to be a problem.

-Steve