for me SmartSet contract does not have to keep the order while UniqueOrderedCol has (at least the order of the first added occurrences of an item.
Stef
On 23 nov. 07, at 15:42, Adrian Kuhn wrote:
What is the difference between UniqueOrderedCollection and SmartSet (except for keyed access)?
I add #unsafeAdd: / #unsafeAddAll: / #assertInvariant to SmartSet.
cheers, AA
On 23 Nov 2007, at 9:02 , Stéphane Ducasse wrote:
fun we should have also UniqueOrderedCollection (should be a couple of methods) BTW UniqueOrderedCollection could also have a fastAdd: (one that does not check uniqueness) if you need large collection and by contract the clients knows that it is responsible of not putting duplicated stuff in there.
Stef
On 22 nov. 07, at 23:46, Adrian Kuhn wrote:
SmartSet represents an unordered collection of elements that are not duplicated.
SmartSet can operate in two modes
- self optimizeGrowth, whereas its values are backed up by a
conventional Set
- self optimizeMemory, whereas its values are backed up by an Array
Other than Set, an attempt to add a duplicate element signals an Error.
AA
On 22 Nov 2007, at 21:32 , Stéphane Ducasse wrote:
Does it make sense to implement and use UniqueOrderedCollection or UniqueArray?
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev