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

Implicit parameters are not checked against contract implied by their sigil in Rakudo #4270

Closed
p6rt opened this issue May 27, 2015 · 4 comments
Labels

Comments

@p6rt
Copy link

p6rt commented May 27, 2015

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

Searchable as RT125260$

@p6rt
Copy link
Author

p6rt commented May 27, 2015

From @masak

* masak discovered a rakudobug!
<masak> m​: sub foo { say &^fn }; foo(42)
<camelia> rakudo-moar c2a57e​: OUTPUT«42␤»
<masak> hah!
<masak> I can't believe none of us has thought of that one before :P
* masak submits it
<raydiak> nice...works with all the sigils
<masak> m​: sub foo(&fn) { say &fn }; foo(42)
<camelia> rakudo-moar c2a57e​: OUTPUT«===SORRY!=== Error while
compiling [...]␤Calling foo(int) will never work with declared
signature (&fn) [...]
<masak> not only is the ordinary form checked, it's *checked at CHECK
time* and never even runs.

@p6rt
Copy link
Author

p6rt commented Jun 4, 2015

From @jnthn

On Wed May 27 10​:57​:47 2015, masak wrote​:

* masak discovered a rakudobug!
<masak> m​: sub foo { say &^fn }; foo(42)
<camelia> rakudo-moar c2a57e​: OUTPUT«42␤»
<masak> hah!
<masak> I can't believe none of us has thought of that one before :P
* masak submits it
<raydiak> nice...works with all the sigils
<masak> m​: sub foo(&fn) { say &fn }; foo(42)
<camelia> rakudo-moar c2a57e​: OUTPUT«===SORRY!=== Error while
compiling [...]␤Calling foo(int) will never work with declared
signature (&fn) [...]
<masak> not only is the ordinary form checked, it's *checked at CHECK
time* and never even runs.

Fixed, and tests added (for all the sigils) in S06-signature/mixed-placeholders.t.

@p6rt
Copy link
Author

p6rt commented Jun 4, 2015

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

@p6rt p6rt closed this as completed Jun 4, 2015
@p6rt
Copy link
Author

p6rt commented Jun 4, 2015

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

@p6rt p6rt added the Bug label Jan 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant