From @coke

09​:55 < [Coke]> nom​: say (-10..10).min​: { abs $^a &lt;=&gt; abs $^b }09​:55
<+p6eval> nom 17a235​: OUTPUT«Too many positional parameters passed;
got 2                but expected 1␤  in method min at
src/gen/CORE.setting​:1232␤                in block <anon> at
/tmp/FOX6arzPat​:1␤  in <anon> at                /tmp/FOX6arzPat​:1␤»

but

09​:56 < [Coke]> nom​: say (1,4,-2).min​: { abs $^a &lt;=&gt; abs $^b }09​:56
<+p6eval> nom 17a235​: OUTPUT«1␤»
This is causing failures in S32-list/minmax.t
--
Will "Coke" Coleda

From @coke

On Thu Dec 01 06​:57​:56 2011, coke wrote​:

09​:55 < [Coke]> nom​: say (-10..10).min​: { abs $^a &lt;=&gt; abs $^b }09​:55
<+p6eval> nom 17a235​: OUTPUT«Too many positional parameters passed;
got 2                but expected 1␤  in method min at
src/gen/CORE.setting​:1232␤                in block <anon> at
/tmp/FOX6arzPat​:1␤  in <anon> at                /tmp/FOX6arzPat​:1␤»

but

09​:56 < [Coke]> nom​: say (1,4,-2).min​: { abs $^a &lt;=&gt; abs $^b }09​:56
<+p6eval> nom 17a235​: OUTPUT«1␤»
This is causing failures in S32-list/minmax.t

Similar issues with Range's "max" also.

--
Will "Coke" Coleda

@coke - Status changed from 'new' to 'open'

From kris@shannon.id.au

Range does not do Positional, so it's min is separate from

our multi method min( @​values​: *&by )

and should not take any arguments.

From kris@shannon.id.au

This looks like a DUP of #​63716

From @coke

On Tue Dec 27 05​:28​:45 2011, Kris.Shannon wrote​:

This looks like a DUP of #​63716

From that ticket​:

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

Rejecting ticket.

--
Will "Coke" Coleda

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