-
Notifications
You must be signed in to change notification settings - Fork 1
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
enum A <Code> "P6opaque: no such attribute '$!signature'" #3612
Comments
From @raiphSee http://irclog.perlgeek.de/perl6/2014-12-19#i_9827480​: naddiseo m: enum A <Block>;subset B; raiph m: subset B raiph m: enum A <Code> Fwiw #123407 gives a similar error. -- |
From @jnthnOn Thu Dec 18 19:01:29 2014, raiph wrote:
Code, Block, etc. are the names of types used to construct code objects, and these are currently resolved using normal lexical scoping rules. Therefore, hiding them with other symbols that don't uphold the expected contract with the compiler is going to lead to things like this. The issue first needs a decision at design level: how should such types be located? One option is to only ever look for them in the currently effective SETTING, for example. |
The RT System itself - Status changed from 'new' to 'open' |
From @AlexDanielThis was fixed in (2015-12-13) rakudo/rakudo@3c81e33 W4anD0eR96++ added tests in Raku/roast@89a96af777 Closing. On 2015-01-08 12:47:58, jnthn@jnthn.net wrote:
|
@AlexDaniel - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#123457 (status was 'resolved')
Searchable as RT123457$
The text was updated successfully, but these errors were encountered: