It does; and I figured something like that was what was going on. I'm just surprised that the metaobject protocol doesn't account for inherited wrapper methods when figuring out a derived class' accessor code. Is there any way to direct Moose to continue using the superclass's around modifier, or is this intended to be the correct way of modifying an accessor's result when expecting inheritance that modifies the metaobject?

use strict;
use warnings;
use 5.010;

package My::Base;
use Moose;

has 'attr' => (is => 'ro', isa => 'Str', required => 1, reader => '_at
+tr');

sub attr {
  my $self = shift;
  return "The value of attr is '".$self->_attr."'"
};

package My::Derived;
use Moose;

extends 'My::Base';

has '+attr' => (required => 0, lazy_build => 1);

sub _build_attr {
  return "default value";
}

package main;
use Test::More tests => 6;
use Test::Exception;

throws_ok {My::Base->new()} qr/Attribute \(attr\) is required/, q/base
+ requires 'attr' at construction/;
my $base = new_ok('My::Base' => [attr => 'constructor value']);
cmp_ok($base->attr, 'eq', "The value of attr is 'constructor value'", 
+'base is correct');
lives_ok {My::Derived->new()} q/derived doesn't require 'attr' at cons
+truction/;
my $der = new_ok('My::Derived');
cmp_ok($der->attr, 'eq', "The value of attr is 'default value'", 'deri
+ved is correct');
[download]