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
Null PMC bug when code confused as hash #1211
Comments
From @colomoncolomon: rakudo: (1..3).map({$_ => $_*$_}).perl.say I understand that this code should not work, but it shouldn't Null PMC On the other hand, not sure if this one should work or not: colomon: rakudo: (1..3).map({$_ => $_*$_;}).perl.say -- |
From @bbkrIt's ppabian@b-gr-dev:~/rakudo$ perl6 -e '(1..3).map({$_ => $_*$_}).perl.say' on Moscow build. |
The RT System itself - Status changed from 'new' to 'open' |
From @bbkrAnd $ perl6 -e '(1..3).map({$_ => $_*$_}).perl.say' on Kiev build |
From @bbkrNOM bbkr:nom bbkr$ ./perl6 -e '(1..3).map({$_ => $_*$_}).perl.say' |
From @diakopterOn Sun Sep 11 02:50:58 2011, bbkr wrote:
new behavior. However, note what happens when I add another {} around 15:50 < diakopter> r: (1..3).map({$_ => $_*$_}).perl.say |
From @moritzNow tested in S06-other/anon-hashes-vs-blocks.t |
@moritz - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#68298 (status was 'resolved')
Searchable as RT68298$
The text was updated successfully, but these errors were encountered: