From @AlexDaniel

Code​:
say ^5 .BagHash.pickpairs(2.5);

Result​:
(1 => 1 4 => 1)

Code​:
say ^5 .BagHash.pick(2.5);

Result​:
count computed to 2.5, which cannot be used
  in block <unit> at <tmp> line 1

I find it impossible to predict when non-Int args are alright and when they are not. I would expect consistency of some sort.

(same thing with .grab and .grabpairs)

From @lizmat

Fixed with 31be51284e70badd8ed , tests needed.

On 8 May 2017, at 20​:25, Aleks-Daniel Jakimenko-Aleksejev (via RT) <perl6-bugs-followup@​perl.org> wrote​:

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

Code​:
say ^5 .BagHash.pickpairs(2.5);

Result​:
(1 => 1 4 => 1)

Code​:
say ^5 .BagHash.pick(2.5);

Result​:
count computed to 2.5, which cannot be used
in block <unit> at <tmp> line 1

I find it impossible to predict when non-Int args are alright and when they are not. I would expect consistency of some sort.

(same thing with .grab and .grabpairs)

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

From @dogbert17

On Mon, 08 May 2017 11​:51​:25 -0700, elizabeth wrote​:

Fixed with 31be51284e70badd8ed , tests needed.

On 8 May 2017, at 20​:25, Aleks-Daniel Jakimenko-Aleksejev (via RT)
<perl6-bugs-followup@​perl.org> wrote​:

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

Code​:
say ^5 .BagHash.pickpairs(2.5);

Result​:
(1 => 1 4 => 1)

Code​:
say ^5 .BagHash.pick(2.5);

Result​:
count computed to 2.5, which cannot be used
in block <unit> at <tmp> line 1

I find it impossible to predict when non-Int args are alright and
when they are not. I would expect consistency of some sort.

(same thing with .grab and .grabpairs)

Tests added with Raku/roast@68d34de4b8. Resolving issue.

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