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

Please migrate module from using deprecated Any:Moose to Moo #5

Open
Corin-EU opened this issue Mar 31, 2017 · 1 comment
Open

Please migrate module from using deprecated Any:Moose to Moo #5

Corin-EU opened this issue Mar 31, 2017 · 1 comment

Comments

@Corin-EU
Copy link

Corin-EU commented Mar 31, 2017

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

DEPRECATION

日本語翻訳: http://blog.64p.org/entry/2013/02/06/094906

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.

@intrigeri
Copy link

This was also reported to CPAN RT in 2015: https://rt.cpan.org/Ticket/Display.html?id=104943.

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?

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

No branches or pull requests

2 participants