From @bacek

src/classes/Range.pir | 12 ++++++++++++
1 files changed, 12 insertions(+), 0 deletions(-)

From @bacek

diff --git a/src/classes/Range.pir b/src/classes/Range.pir
index 6b7eeb9..4cdb54f 100644
--- a/src/classes/Range.pir
+++ b/src/classes/Range.pir
@@ -137,11 +137,23 @@ just return a clone of the Range.
 .namespace ['Range']
 
 .sub 'max' :method
+    .param pmc by       :optional
+    .param int has_by   :opt_flag
+    if has_by goto have_by
     .tailcall self.'to'()
+  have_by:
+    $P0 = self.'list'()
+    .tailcall $P0.'max'(by)
 .end
 
 .sub 'min' :method
+    .param pmc by       :optional
+    .param int has_by   :opt_flag
+    if has_by goto have_by
     .tailcall self.'from'()
+  have_by:
+    $P0 = self.'list'()
+    .tailcall $P0.'min'(by)
 .end
 
 .sub 'minmax' :method

From @pmichaud

On Sat Mar 07 21​:58​:33 2009, bacek wrote​:

---
src/classes/Range.pir | 12 ++++++++++++
1 files changed, 12 insertions(+), 0 deletions(-)

Patch rejected. S03​:2885 describes slightly different semantics for
.min and .max in Ranges, and doesn't mention an Ordering parameter at all.

If the synopses are later modified so that Range.min and Range.max
accept an Ordering $by parameter, I suspect the end result will be that
we inherit .min and .max from Any in that case.

Thanks for submitting!

Pm

The RT System itself - Status changed from 'new' to 'open'

@pmichaud - Status changed from 'open' to 'rejected'