You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add a lexical, compile time switch to allow the user to choose which type system will be used, Moose or Mouse (or a 3rd thing we may add in the future). This would override Any::Moose.
It could be used both for performance and for a non-M[ou]se class to decide which set of types it wants to use.
Disagree. Detecting what the class is already using, with Any::Moose as default, is a good solution. If a user controls Any::Moose, he controls MS and anything else using it.
package Foo;
use Method::Signatures; # uses Any::Moose to resolve Foo's type checks (the default)
package Bar;
use Mouse;
use Method::Signatures; # uses Mouse for Bar' s methods because Bar isa Mouse (as proposed in #34)
package Baz;
use Method::Signatures { types => "Moose" }; # uses Moose for Baz because the user asked for it
And I don't think I understand what "if a user controls Any::Moose, he controls MS and anything else using it" means. Could you explain?
Add a lexical, compile time switch to allow the user to choose which type system will be used, Moose or Mouse (or a 3rd thing we may add in the future). This would override Any::Moose.
It could be used both for performance and for a non-M[ou]se class to decide which set of types it wants to use.
Related to #34.
The text was updated successfully, but these errors were encountered: