From @smls

Currently, calling .min or .max on an non-empty Hash throws a spurious error​:

  ➜ say {a=>3, b=>2, c=>1}.max(*.value);
  Index out of range. Is​: 1, should be in 0..0

  ➜ say {a=>3, b=>2, c=>1}.min(*.value);
  Index out of range. Is​: 1, should be in 0..0

I think they should operate on the Hash is list context (i.e. make .max work like .list.max, and .min like .list.min).

That's what other list'y methods already do when they're used on a Hash​:

  ➜ say {a=>3, b=>2, c=>1}.grep(*.value == 3);
  (a => 3)

  ➜ say {a=>3, b=>2, c=>1}.sort(*.value)
  (c => 1 b => 2 a => 3)

From @lizmat

This is a side effect of min/max/minmax not using an iterator approach atm. I’m looking at making the necessary modifications, but that will be later today at the soonest.

On 30 Jul 2016, at 11​:47, Sam S. (via RT) <perl6-bugs-followup@​perl.org> wrote​:

# New Ticket Created by Sam S.
# Please include the string​: [perl #​128780]
# in the subject line of all future correspondence about this issue.
# <URL​: https://rt-archive.perl.org/perl6/Ticket/Display.html?id=128780 >

Currently, calling .min or .max on an non-empty Hash throws a spurious error​:

➜ say {a=>3, b=>2, c=>1}.max(*.value);
Index out of range. Is​: 1, should be in 0..0

➜ say {a=>3, b=>2, c=>1}.min(*.value);
Index out of range. Is​: 1, should be in 0..0

I think they should operate on the Hash is list context (i.e. make .max work like .list.max, and .min like .list.min).

That's what other list'y methods already do when they're used on a Hash​:

➜ say {a=>3, b=>2, c=>1}.grep(*.value == 3);
(a => 3)

➜ say {a=>3, b=>2, c=>1}.sort(*.value)
(c => 1 b => 2 a => 3)

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

From @lizmat

Fixed with 1035edb , tests needed

On 30 Jul 2016, at 11​:47, Sam S. (via RT) <perl6-bugs-followup@​perl.org> wrote​:

# New Ticket Created by Sam S.
# Please include the string​: [perl #​128780]
# in the subject line of all future correspondence about this issue.
# <URL​: https://rt-archive.perl.org/perl6/Ticket/Display.html?id=128780 >

Currently, calling .min or .max on an non-empty Hash throws a spurious error​:

➜ say {a=>3, b=>2, c=>1}.max(*.value);
Index out of range. Is​: 1, should be in 0..0

➜ say {a=>3, b=>2, c=>1}.min(*.value);
Index out of range. Is​: 1, should be in 0..0

I think they should operate on the Hash is list context (i.e. make .max work like .list.max, and .min like .list.min).

That's what other list'y methods already do when they're used on a Hash​:

➜ say {a=>3, b=>2, c=>1}.grep(*.value == 3);
(a => 3)

➜ say {a=>3, b=>2, c=>1}.sort(*.value)
(c => 1 b => 2 a => 3)

From @zoffixznet

Tests added in Raku/roast@9b9c39ae08

--
Cheers,
ZZ | https://twitter.com/zoffix

@zoffixznet - Status changed from 'open' to 'resolved'