Skip to content
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

Diagnostic for that weird error we just got #1

Merged
merged 1 commit into from
Oct 5, 2013
Merged

Conversation

mjdominus
Copy link

If the target of the composed behavior is not a Moose class, the call
to 'apply_all_roles' will fail with a bizarre error message. This
cann occur if, for example, your "use Moose" declaration follows the
"use MooseX::ComposedBehavior" declaration in the target file.

Moose itself should diagnose this more clearly, but in the meantime we
add a diagnosis here.

If the target of the composed behavior is not a Moose class, the call
to 'apply_all_roles' will fail with a bizarre error message.  This
cann occur if, for example, your "use Moose" declaration follows the
"use MooseX::ComposedBehavior" declaration in the target file.

Moose itself should diagnose this more clearly, but in the meantime we
add a diagnosis here.
@rjbs rjbs merged commit 6812641 into rjbs:master Oct 5, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants