projects / gitmo/Moose.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 18b28ba)
Test (that fails) for an edge case in role composition
authorDave Rolsky <autarch@urth.org>
Fri, 6 Jan 2012 20:59:07 +0000 (14:59 -0600)
committerDave Rolsky <autarch@urth.org>
Fri, 6 Jan 2012 20:59:07 +0000 (14:59 -0600)
commitcd96b99819007e8605a5f808ef587e78f93a88f5
tree2b033beb848c5d24c9715937a03d6e1d2e822211tree | snapshot
parent18b28ba887282651b2c4e3cf4cf2e8cc49e05d9ecommit | diff
Test (that fails) for an edge case in role composition

When composing three roles, it is possible for the composite to end up with
both a conflict on a method and a method of that name. In most practical
applications, this doesn't really matter, since the conflict causes an
exception that must be resolved by the consumer.

However, it means that the composite reports bogus information when has_method
or get_method() is called.
t/roles/role_composition_conflict_detection.t [new file with mode: 0644] blob
A Postmodern Object System for Perl5 - now lives at https://github.com/moose/Moose