Generally speaking, the storage strategy should be dissociated from the
hashed functionality that is to be provided. In other words, open
addressing linear probing and hash buckets should be swappable under set
(or dictionary, etc).
On 10/18/10 9:31 , Stéphane Ducasse wrote:
and we should clean it because it was introduced a bit fast in pharo :)
On Oct 18, 2010, at 12:29 PM, Igor Stasenko wrote:
HashedCollection is an abstract base class, which contains common
behavior for all hash-based collections,
including Set, Dictionary etc.
On 18 October 2010 13:04, Benjamin Van Ryseghem
<[email protected]> wrote:
I was looking in Pharo sources and I do not understand the difference
between Set and HashedCollection which both seems to work the same way.
Benjamin
_______________________________________________
Pharo-users mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users
--
Best regards,
Igor Stasenko AKA sig.
_______________________________________________
Pharo-users mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users
_______________________________________________
Pharo-users mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users
_______________________________________________
Pharo-users mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users
