Hey,
So I was starting to play with Reaction and I noticed that the latest
Moose was causing it to throw warnings for some stuff and tracking it
down it seemed Moose was being overly zellous about it's warnings
about overriding local methods with accessors. The following test
illustrates the behavior:
package Role;
use Moose::Role;
has value => (
is => 'rw',
clearer => 'clear_value',
);
after clear_value => sub { };
package Class;
use Moose;
with 'Role';
has '+value' => ( isa => q[Str] );
package main;
Class->new;
I tracked this down and fixed the issue in
topic/check_original_wrapped_method which basically unwraps wrapped
methods until it gets back to the original method, then proceeds to
run the checks. Are there other instances where we could run into a
similar situation? (ie that we need to dig a bit till we find the
*actual* method we're overriding) ... possibly in the new Aliased
methods?
-Chris
