We merged ~60 PRs this week.
# Pharo 11
- Backport #13426: Make protocol of super method a priority in MethodClassifier
#13432
https://github.com/pharo-project/pharo/pull/13432
- Use fixed spec version for Pharo 11 #13445
https://github.com/pharo-project/pharo/pull/13445
Hi Richard,
Now that's much clearer to me:
min{y | y in c . y > x} "strict supremum"
max{y | y in c . y < x} "strict infimum"
For the general case of a sequence (not sorted) of elements we can do
strictSupremumOf: x in: sequence
^(sequence transduce
I'm sorry, it appears that I failed to explain the question
well enough. I thought I'd explained earlier.
successor: target
^(self select: [:each | target < each]) min
is trivial. What's wrong with it is that it allocates
an intermediate collection and takes two passes.
FIXING that is is
