>> Not really :) >> I was more looking at the user perspective. >> You often want an orderedCollection (add:) vs Array at: >> but which deals with duplicate as a Set. > > Could you clarify? What's an example?
In Moose we build package representation in which the order is important first references is more important that second. Now my colleagues used an OrderedSet to keep the order but make sure that he can use add: (but did not care of possible duplicates). > What is the index of something > that you add but was already there? >From his example the index is more important per se as soon as the order is kept since after he iterates on this data structure to build visualization. > > Regards, > > -Martin > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
