How did you know I implemented that? hahahah ;)
Now seriously, I am still not convinced on the decision on way to do that automatically or not..that is...the #shouldSearchForAllStandardDelimiters
I evaluated, and still is in my mind, to use an explicit new boolean instVar to control that.... but so far, I am still not convinced.
BTW, to implement that functionally and be it performant, we also implemented new primitives which allowed speedup in other areas too.
Below some notes from our interna bug tracker:
"- New methods in SequenceableCollection
indexOfAny: aSequenceableCollection
indexOfAny: aSequenceableCollection ifAbsent: exceptionBlock
indexOfAny: aSequenceableCollection startingAt: start
indexOfAny: aSequenceableCollection startingAt: start ifAbsent: exceptionHandler
- These 4 methods give symmetry with indexOfSubCollection...
- indexOfAny will answer the index of the first element to be in the argument aSequenceableCollection
- Implemented VMprStringIndexOfAny prim
This will provide String/DBString specific prim-assist for character searches using indexOfAny.... It's about 3-4x faster than using the more generic version in SequenceableCollection.
These also went on all the other streams that have the new delimiter handlers.
skipToAny: aSequentialCollection
upToAny: aSequentialCollection
"
create a generic/reusable and FAST #indexOfAny:* , #skipToAny: and #upToAny:
So basically.... all these #indexOfAny:*, #skipToAny: and #upToAny: are now prim assisted and fast.