-
Notifications
You must be signed in to change notification settings - Fork 1
Some sort of a scoping bug when variables are used inside a closure in a &sub.wrap call in Rakudo #1309
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
Comments
From @masak<masak> rakudo: sub foo { say "=" x 40 }; for reverse ^40 -> $n { I'm not certain this is a bug. But if Perl 6 doesn't conform to my |
From @jnthnOn Wed Sep 23 03:14:06 2009, masak wrote:
OUTPUT«========================================»
OUTPUT«39383736353433323130292827262524232221201918171615141312111098765432100000000000000000000000000000000000000000400000000000000
Now it makes you a nice triangle:
================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================ Tagging as "testneeded". /jnthn |
The RT System itself - Status changed from 'new' to 'open' |
From @moritzNow tested in S06-advanced/wrap.t |
@moritz - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#69312 (status was 'resolved')
Searchable as RT69312$
The text was updated successfully, but these errors were encountered: