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

LTA error message when using permutations with negative parameter (permutations -1) #5195

Closed
p6rt opened this issue Mar 24, 2016 · 6 comments

Comments

@p6rt
Copy link

p6rt commented Mar 24, 2016

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

Searchable as RT127777$

@p6rt
Copy link
Author

p6rt commented Mar 24, 2016

From @AlexDaniel

Code​:
permutations -1

Result​:
Constraint type check failed for parameter '$n'
  in block <unit> at -e line 1

There's no “$n” in my code, so it should not mention it.

@p6rt
Copy link
Author

p6rt commented Mar 26, 2016

From @lizmat

Fixed with 1d12563b6c2cb39 , tests needed

On 24 Mar 2016, at 21​:40, Alex Jakimenko (via RT) <perl6-bugs-followup@​perl.org> wrote​:

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

Code​:
permutations -1

Result​:
Constraint type check failed for parameter '$n'
in block <unit> at -e line 1

There's no “$n” in my code, so it should not mention it.

@p6rt
Copy link
Author

p6rt commented Mar 26, 2016

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

@p6rt
Copy link
Author

p6rt commented Apr 11, 2016

From @usev6

I addes a test to S32-list/permutations.t with commit Raku/roast@30db58671d

I'm closing this ticket as 'resolved'.

1 similar comment
@p6rt
Copy link
Author

p6rt commented Apr 11, 2016

From @usev6

I addes a test to S32-list/permutations.t with commit Raku/roast@30db58671d

I'm closing this ticket as 'resolved'.

@p6rt
Copy link
Author

p6rt commented Apr 11, 2016

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant