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

Required named occurring before slurpy wrongly considered a multi candidate in Rakduo #3164

Closed
p6rt opened this issue Jun 13, 2013 · 6 comments

Comments

@p6rt
Copy link

p6rt commented Jun 13, 2013

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

Searchable as RT118467$

@p6rt
Copy link
Author

p6rt commented Jun 13, 2013

From @masak

<masak> rn​: multi foo(​:$d!, *@​f) {}; multi foo(*@​f) { say "works" }; foo() #OK
<camelia> rakudo b2072f, niecza v24-75-g480a062​: OUTPUT«works␤»
<masak> rn​: multi foo(*@​f, :$d!) {}; multi foo(*@​f) { say "works" }; foo() #OK
<camelia> niecza v24-75-g480a062​: OUTPUT«works␤»
<camelia> ..rakudo b2072f​: OUTPUT«Ambiguous call to 'foo'; these
signatures all match​:␤​:(*@​f, :d(​:$d)!)␤​:(*@​f) [...]»
* masak submits rakudobug

Niecza has it right both times.

@p6rt
Copy link
Author

p6rt commented Sep 13, 2015

From @usev6

There already was a (skipped) test for this bug in S06-multi/positional-vs-named.t

I added a reference to this ticket with commit Raku/roast@d397bca9f2

1 similar comment
@p6rt
Copy link
Author

p6rt commented Sep 13, 2015

From @usev6

There already was a (skipped) test for this bug in S06-multi/positional-vs-named.t

I added a reference to this ticket with commit Raku/roast@d397bca9f2

@p6rt
Copy link
Author

p6rt commented Sep 13, 2015

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

@p6rt
Copy link
Author

p6rt commented Sep 23, 2015

From @jnthn

On Sun Sep 13 11​:39​:56 2015, bartolin@​gmx.de wrote​:

There already was a (skipped) test for this bug in S06-
multi/positional-vs-named.t

I added a reference to this ticket with commit
Raku/roast@d397bca9f2

Fixed the issue and unfudged the test.

@p6rt
Copy link
Author

p6rt commented Sep 23, 2015

@jnthn - 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