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
threads, dynamic variables lost sometimes #4933
Comments
From @LLFournperl6 -e 'sub t { say #!>Dynamic variable $*d not found Tested on mac and deb. |
From @lizmat
Confirmed. But is there a reason you want to use the do { } block? Without it, it just works! $ 6 'sub t { say Looks like any extra scope breaks it: $ 6 'sub t { say $ 6 'sub t { say Liz |
The RT System itself - Status changed from 'new' to 'open' |
From @LLFournZoffix++ lead to the discovery of a similar bug which can be golfed to: 00:16 < llfourn> m: my if you put the block outside the start {} you don't get an error but you On Sun, Dec 27, 2015 at 7:06 AM Elizabeth Mattijsen via RT <
|
From @smlsAll the examples in this thread work fine for me, on 64bit Linux with current Rakudo. This is Rakudo version 2016.09-163-g92c0921 built on MoarVM version 2016.09-39-g688796b Has the bug been fixed, or is it platform-dependent? |
From @smlsIt really seems to have been fixed. (Fails with older Rakudo revisions but works with newer ones on the same system). Bisectable identifies the following as the commit that fixed it (both the original test-case and Zoffix's one): Marking as [test needed]. |
From @LLFournlooks like it's been fixed! \o/ I will put writing test for this on my TODO. On Tue, Oct 11, 2016 at 5:00 AM Sam S. via RT <perl6-bugs-followup@perl.org> All the examples in this thread work fine for me, on 64bit Linux with This is Rakudo version 2016.09-163-g92c0921 built on MoarVM version Has the bug been fixed, or is it platform-dependent? |
From @LLFournTests: On Tue, Oct 11, 2016 at 9:26 PM Lloyd Fournier <lloyd.fourn@gmail.com>
|
@smls - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#127033 (status was 'resolved')
Searchable as RT127033$
The text was updated successfully, but these errors were encountered: