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
Please use Moo instead of Any::Moose for new code.
Moo classes and roles will transparently and correctly upgrade to Moose when needed. This is a fundamentally better design than what Any::Moose offers. Mouse metaclasses do not interact with Moose metaclasses which leaks abstractions all over the place.
Any::Moose had a good run. It was a simplistic but expedient answer for getting Moose syntax on the cheap but with the transparent upgrade path to Moose when you needed it. But really, please don't use it any more. :)
You may find MooX::late useful for porting your code from Any::Moose to Moo.
The text was updated successfully, but these errors were encountered:
I understand that solving this issue boils down to removing MouseX::Types::Moose and the corresponding tests, so it looks like a social decision to make rather than a difficult technical problem. Is this correct?
Would you be amenable to dropping Any::Moose support?
MouseX::Types requires: Any::Moose: 0.15
Any::Moose has been deprecated since February 2013 (over FOUR years ago at the time of writing).
Please migrate MouseX::Types to use Moo instead.
From the MetaCPAN page for Any::Moose at https://metacpan.org/pod/Any::Moose
The text was updated successfully, but these errors were encountered: