-
Notifications
You must be signed in to change notification settings - Fork 1
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
42 but False #4689
Comments
From @cokeThis test from integration/advent2010-day19.t works on moar, but not on the JVM. 16:33 < [Coke]> r: my $value = 42 but False; say ?$value; -- |
From @peschwaOn Thu Oct 29 13:35:04 2015, coke wrote:
http://irclog.perlgeek.de/p6dev/2016-04-07#i_12299830 has my findings regarding this bug. Unfortunately nothing that points towards a fix, but at least some digging regarding what's happening. |
The RT System itself - Status changed from 'new' to 'open' |
From @usev6For the records: This works with '--optimize=off' (as psch++ has shown in the linked discussion on #perl6). $ ./perl6-j --optimize=off -e 'my $value = 42 but False; say ?$value' The optimizer adds a QAST::Want for the mixin which the JVM backend does not handle correctly. $ RAKUDO_OPTIMIZER_DEBUG=1 ./perl6-j -e 'my $value = 42 but False; say ?$value' See also my findings in https://rt-archive.perl.org/perl6/Ticket/Display.html?id=129782 which is about a similar problem. |
1 similar comment
From @usev6For the records: This works with '--optimize=off' (as psch++ has shown in the linked discussion on #perl6). $ ./perl6-j --optimize=off -e 'my $value = 42 but False; say ?$value' The optimizer adds a QAST::Want for the mixin which the JVM backend does not handle correctly. $ RAKUDO_OPTIMIZER_DEBUG=1 ./perl6-j -e 'my $value = 42 but False; say ?$value' See also my findings in https://rt-archive.perl.org/perl6/Ticket/Display.html?id=129782 which is about a similar problem. |
From @usev6Fixed with Raku/nqp@2d88d98201 I'm closing this ticket as 'resolved'. |
1 similar comment
From @usev6Fixed with Raku/nqp@2d88d98201 I'm closing this ticket as 'resolved'. |
@usev6 - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#126491 (status was 'resolved')
Searchable as RT126491$
The text was updated successfully, but these errors were encountered: