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 access when referring to a lexical variable in a scope that has not been run yet in Rakudo #1930
Comments
From @masak<masak> rakudo: sub foo { my $y; our sub bar { say $y } }; bar |
From @kylehaThis is an automatically generated mail to inform you that tests are now available in t/spec/S04-declarations/my.t commit cce068982cf58cf2f71673f12de5262528202010 [t/spec] test for RT #76466# Inline Patchdiff --git a/t/spec/S04-declarations/my.t b/t/spec/S04-declarations/my.t
index 68b5bc0..c02ddac 100644
--- a/t/spec/S04-declarations/my.t
+++ b/t/spec/S04-declarations/my.t
@@ -232,9 +232,10 @@ my $z = 42;
}
}
-# used to be RT #76366
+# used to be RT #76366, #76466
{
- lives_ok { access_lexical_a() },
+ #?rakudo skip 'RT 76466'
+ nok access_lexical_a().defined,
'can call our-sub that accesses a lexical before the block was run';
{
my $a = 42; |
The RT System itself - Status changed from 'new' to 'open' |
From @cokeOn Sun Jul 11 07:07:52 2010, masak wrote:
This no longer generates an NPA: 13:18 < [Coke]> rakudo: sub foo { my $y; our sub bar { say $y } }; bar But moritz thinks this is still incorrect behavior. -- |
From @masakOn Fri Oct 07 10:24:37 2011, coke wrote:
For what it's worth, I don't think it's incorrect behavior. Perl 6 |
From @tadzikThis now fails at CHECK time:
Tests are present, can we close this one? |
@moritz - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#76466 (status was 'resolved')
Searchable as RT76466$
The text was updated successfully, but these errors were encountered: