SequenceableCollection and remove:
Why does SequencableCollection>>#remove:ifAbsent: say self shouldNotImplement ? All the subclasses I've looked at do implement some sort of removal methods. Thomas
Thomas, On 01 Jul 2013, at 22:47, "Thomas Worthington" <thomas@technouveau.co.uk> wrote:
Why does SequencableCollection>>#remove:ifAbsent: say
self shouldNotImplement ?
All the subclasses I've looked at do implement some sort of removal methods.
Thomas
This is by design, you cannot remove elements from SequencableCollections, once created they remain the same size. If you want that, you need OrderedCollection for example. HTH, Sven -- Powering the T3 Platform - http://t3-platform.net Sven Van Caekenberghe - mailto:sven@beta9.be Beta Nine - software engineering - http://www.beta9.be
participants (2)
-
Sven Van Caekenberghe -
Thomas Worthington