We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
&infix:<^^>
^^
Migrated from rt.perl.org#131932 (status was 'open')
Searchable as RT131932$
The text was updated successfully, but these errors were encountered:
The first example below evaluates the code block, while the two examples after it never do and return the block raw.
Is this by design?
<Zoffix_> m: &infix:<^^>(1, -> {say 2}) <camelia> rakudo-moar 2545e6: OUTPUT: «2»
<Zoffix_> m: 1 ^^ -> {say 2} <camelia> rakudo-moar 2545e6: ( no output ) <Zoffix_> m: 0 ^^ -> {say 2} <camelia> rakudo-moar 2545e6: ( no output ) Zoffix_> m: say (0 ^^ -> {say 2}) <camelia> rakudo-moar 2545e6: OUTPUT: «-> { #`(Block|72040712) ... }»
Sorry, something went wrong.
It's the same with && and ||:
➜ &infix:<&&>(1, -> {say 2}); # 2 ➜ say 1 && -> {say 2}; # -> { #`(Block|169403552312) ... }
➜ &infix:<||>(0, -> {say 2}); # 2 ➜ say 0 || -> {say 2}; # -> { #`(Block|786414142008) ... }
And also with the loose-precedence versions `and`, `or`, `xor`.
And also with `xx`:
➜ &infix:<xx>(-> {say 2}, 2) 2 2
➜ say -> {say 2} xx 2 (-> { #`(Block|315591575136) ... } -> { #`(Block|315591575208) ... })
I.e., it's apparently a general rule for "thunky" operators.
Whether it's intentional, I don't know.
The design docs don't mention it: https://design.perl6.org/S03#Tight_and_precedence
The RT System itself - Status changed from 'new' to 'open'
No branches or pull requests
Migrated from rt.perl.org#131932 (status was 'open')
Searchable as RT131932$
The text was updated successfully, but these errors were encountered: