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
.wrap
on an is export
sub doesn't affect it for scopes that already imported it
#2608
Comments
From @masak<tadzik> about wrap again: https://gist.github.com/1585730 Included here for completeness: ┌─[tadzik@yavin4]─[~/src/perl/bailador] (master)* our sub our_template { sub exp_template is export { sub hook is export { sub foo { hook(); foo(); <masak> tadzik: looks like a bug to me. S11:137: Importing via C<use> binds into the current lexical scope by default <masak> tadzik: will you submit a rakudobug, or shall I? |
From @smlsOn Tue, 10 Jan 2012 02:16:07 -0800, masak wrote:
This bug is still present in current Rakudo: This is Rakudo version 2017.08-104-g76f1d8970 (Test script now needs s/module/unit module/ to run, but then produces the same result.) Calling `&exp_template.WHICH` also confirms that the one in the module and the one in the mainline scope are different objects. |
The RT System itself - Status changed from 'new' to 'open' |
Migrated from rt.perl.org#107844 (status was 'open')
Searchable as RT107844$
The text was updated successfully, but these errors were encountered: