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
'next' or 'last' don't trigger LEAVE phaser in loop in Rakudo #2806
Comments
From @masak<masak> r: loop { last; LEAVE say "bye!" }; say "outside" Niecza has the behavior I'd expect from Rakudo. |
From @cokeOn Mon Jul 02 07:02:11 2012, masak wrote:
Behavior has changed; we're half right: 20:02 < [Coke]> r: loop { last; LEAVE say "bye!" }; say "outside" -- |
The RT System itself - Status changed from 'new' to 'open' |
From @usev6As noted in April 'next' triggers LEAVE phaser as expected. With 'last' there is no longer an error, but the LEAVE phaser is still not triggered (same output on Moar, Parrot and JVM): $ perl6 -e 'loop { last; LEAVE say "bye!" }; say "outside"' I added two tests (the one for 'last' is fuged 'todo') to S04-phasers/enter-leave.t with commit Raku/roast@bba16ae7e0 |
1 similar comment
From @usev6As noted in April 'next' triggers LEAVE phaser as expected. With 'last' there is no longer an error, but the LEAVE phaser is still not triggered (same output on Moar, Parrot and JVM): $ perl6 -e 'loop { last; LEAVE say "bye!" }; say "outside"' I added two tests (the one for 'last' is fuged 'todo') to S04-phasers/enter-leave.t with commit Raku/roast@bba16ae7e0 |
From @jnthnOn Sun Nov 23 00:10:12 2014, bartolin@gmx.de wrote:
Was an optimizer issue; it over-eagerly flattened away the loop block, losing the exit handler in the process. Fixed, and test unfudged. |
@jnthn - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#113950 (status was 'resolved')
Searchable as RT113950$
The text was updated successfully, but these errors were encountered: