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
Stubbed attributes in roles don't die at compose time like stubbed methods do in Rakudo #3303
Comments
From @masak<FROGGS> I could just make a role (Slangy) that stubs attributes... I'm not aware that the spec requires stubbed attributes to blow up at Even if we arrive at the conclusion that stubbed attributes in roles |
From @TimToadyThe purpose of stubbing is to guarantee the public interface is complete, and since the public interface of attributes is entirely via accessors, it suffices to merely stub the accessor, and leave it up to the class whether it should implement that name via an explicit method or an attribute declaration. It should probably be part of the documentation of a role whether it's intended that a particular name be implemented by by an attribute, but really, it's entirely up to the class whether a given part of the interface is represented by an actual attribute or a virtual attribute. Larry |
The RT System itself - Status changed from 'new' to 'open' |
@TimToady - Status changed from 'open' to 'rejected' |
Migrated from rt.perl.org#120916 (status was 'rejected')
Searchable as RT120916$
The text was updated successfully, but these errors were encountered: