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
infix:<,=> should have list precedence in the cases infix:<=> does in Rakudo #1915
Comments
From @masak<tylercurtis> rakudo: my @foo; push(@foo, 1, 2, 3); @foo.perl.say |
@coke - Status changed from 'new' to 'open' |
From @cokeOn Wed Jul 07 15:35:30 2010, masak wrote:
This now fails with: 20:44 < [Coke]> rakudo: my @foo; @foo ,= 1, 2, 3; @foo.perl.say -- |
From @moritzBack to the original state: 09:10 < moritz> rakudo: my @foo; @foo ,= 1, 2, 3; @foo.perl.say |
From @usev6This now emits a warning about useless use of "," in sink context, but the result hasn't changed: $ perl6 -e 'my @foo; @foo ,= 1, 2, 3; @foo.perl.say' I added a test (fudged "todo") to S03-operators/assign.t with commit Raku/roast@3e737ee253 |
1 similar comment
From @usev6This now emits a warning about useless use of "," in sink context, but the result hasn't changed: $ perl6 -e 'my @foo; @foo ,= 1, 2, 3; @foo.perl.say' I added a test (fudged "todo") to S03-operators/assign.t with commit Raku/roast@3e737ee253 |
From @MouqFixed in Rakudo commit: commit 34669da476fb9cce4e55ffdc72e89d3dded83cf0 Improve metaop:<=> Dies in the case of fiddly/diffy operators, and now adjusts to the Behavior now: $ perl6 -e 'my @foo; @foo ,= 1, 2, 3; @foo.perl.say' Marking as resolved :) On Sat Nov 22 02:22:41 2014, bartolin@gmx.de wrote:
|
@Mouq - Status changed from 'open' to 'resolved' |
I don't think we will ever follow S03 on that, as that implies too much magic DWIM, and a big WAT! Associated ticket: Raku/old-issue-tracker#1915
#1915 adapted test to match post-GLR behaviour |
Migrated from rt.perl.org#76414 (status was 'resolved')
Searchable as RT76414$
The text was updated successfully, but these errors were encountered: