-
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
Private methods on roles are too attached to their own invocant type #4443
Comments
From @moritzRelated to, but distinct from RT #125606: role A { method !foo(A:D:) { say "success!" } }; C.new.bar(); # dies with "Stub code executed" If one puts method bar into class C, it works. I think it should also work with method bar in role B: both the public FWIW this is not an optimizer bug; running with --optimize=off produces So I guess the code could be changed to generate to calls if $type.^is-role { |
From @jnthnOn Sun Jul 26 08:50:43 2015, moritz wrote:
You just late-bound it to look up ::?CLASS when inside of a role. Fixed, and added test in S14-roles/stub.t. |
The RT System itself - Status changed from 'new' to 'open' |
@jnthn - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#125694 (status was 'resolved')
Searchable as RT125694$
The text was updated successfully, but these errors were encountered: