Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

.pick and .pickpairs with negative amounts ( say ^5 .BagHash.pickpairs(-2.5) ) #6229

Closed
p6rt opened this issue May 8, 2017 · 4 comments
Closed
Labels
regression Issue did not exist previously

Comments

@p6rt
Copy link

p6rt commented May 8, 2017

Migrated from rt.perl.org#131273 (status was 'resolved')

Searchable as RT131273$

@p6rt
Copy link
Author

p6rt commented May 8, 2017

From @AlexDaniel

Not a big deal as it was changed yesterday, but still​:

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

Result​:
(3 0 1 4 2)

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

Result​:
Unable to allocate an array of 18446744073709551614 elements
  in block <unit> at /tmp/p5a9fTqCqs line 1

For the last one, bisectable points to rakudo/rakudo@0f21f51

This ticket is probably already resolved by lizmat++, but I thought I'll file it anyway so that it doesn't fall through the cracks (seems like there are no tests for these cases?).

@p6rt
Copy link
Author

p6rt commented Jul 5, 2017

From @dogbert17

On Mon, 08 May 2017 12​:01​:56 -0700, alex.jakimenko@​gmail.com wrote​:

Not a big deal as it was changed yesterday, but still​:

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

Result​:
(3 0 1 4 2)

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

Result​:
Unable to allocate an array of 18446744073709551614 elements
in block <unit> at /tmp/p5a9fTqCqs line 1

For the last one, bisectable points to
rakudo/rakudo@0f21f51

This ticket is probably already resolved by lizmat++, but I thought
I'll file it anyway so that it doesn't fall through the cracks (seems
like there are no tests for these cases?).

Tests added in Raku/roast@d05653ace7. Resolving issue.

@p6rt
Copy link
Author

p6rt commented Jul 5, 2017

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

@p6rt
Copy link
Author

p6rt commented Jul 5, 2017

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

@p6rt p6rt closed this as completed Jul 5, 2017
@p6rt p6rt added the regression Issue did not exist previously label Jan 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
regression Issue did not exist previously
Projects
None yet
Development

No branches or pull requests

1 participant