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
Issues when sub itself instead of its "dispatcher" used in sub EXPORT #6331
Comments
From @zoffixznetFrom what I understand subs—even `only` subs—have another Sub playing the role of a dispatcher or whatever: m: sub foo {}.WHERE.say; &foo.WHERE.say And it seems when the sub itself, instead of this "dispatcher", is used in sub EXPORT in a precompiled m: sub foo {}.WHERE.say; &foo.WHERE.say Doing any of the following fixes the above bug: - adding `no precompilation` to Foo.pm6 |
From @LLFournI think this is just another example of the compile time closures problem https://rt.perl.org/Public/Bug/Display.html?id=128636 For an example in my own code: https://github.com/spitsh/spitsh/blob/master/lib/Spit/Constants.pm6 I can't put that sub definition in the constant assignment because it runs On Thu, Jun 8, 2017 at 2:31 AM Zoffix Znet <perl6-bugs-followup@perl.org>
|
The RT System itself - Status changed from 'new' to 'open' |
Migrated from rt.perl.org#131528 (status was 'open')
Searchable as RT131528$
The text was updated successfully, but these errors were encountered: