| Subject: | wishlist: Allow for explicit method exclusion in role composition |
Here's the situation. I have a role which does several other roles,
let's call it MasterRole. It does RoleA and RoleB.
RoleA and RoleB each provide one method, let's call them a() and b().
MasterRole provides its own implementations of a() and b().
Right now, when I have a class (call it Consumer) that does MasterRole,
I get an error that a() and b() are required methods.
If I could manually exclude a() and b() in MasterRole, that would solve
the problem. This is what I did when I was using Class::Trait for this
functionality, but I'm trying to move this code over to Moose.