Skip Menu |
 

This queue is for tickets about the Moose CPAN distribution.

Report information
The Basics
Id: 69207
Status: open
Priority: 0/
Queue: Moose

People
Owner: Nobody in particular
Requestors: DOHERTY [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Wishlist
Broken in: (no value)
Fixed in: (no value)



Subject: Automatically import namespace::autoclean
Download (untitled) / with headers
text/plain 634b
Just like Moose does for strict and warnings, namespace::autoclean should automatically be loaded to clean up Moose droppings and other nonsense after you're done Moosey things. Notes: - rjbs said it causes action at a distance - autarch said he'd be happy if it did autoclean, because it is a no- brainer - rafl mentioned that including MooseX::Role::WithOverloading in core could help - doy said it can break legacy software - and that it won't work well enough until there's a reliable way to distinguish between methods and subroutines - and that it breaks overloading - and that I might eventually get my pony in 2.04
We can't consider this until after MooseX::WithOverloading is cored.
Download (untitled) / with headers
text/plain 630b
FWIW, I wish Moose would stop auto-importing any other modules. At work, this has been a huge been a constant source of pain. We have our own pragma that enables various experimental features (like signatures) and disables warnings for those features. If we use Moose or anything else that uses Moose::Exporter _after_ we use our pragma, Moose re-enables the experimental warnings. I think the "automatically adds a bunch of other stuff" behavior is generally a bad idea for any sort of lower level tool like Moose. This is best reserved for highly opinionated things like corporate-internal pragmas or a higher-level framework.
Download (untitled) / with headers
text/plain 750b
On Sun Sep 11 14:32:32 2016, DROLSKY wrote: Show quoted text
> FWIW, I wish Moose would stop auto-importing any other modules. > > At work, this has been a huge been a constant source of pain. We have > our own pragma that enables various experimental features (like > signatures) and disables warnings for those features. If we use Moose > or anything else that uses Moose::Exporter _after_ we use our pragma, > Moose re-enables the experimental warnings. > > I think the "automatically adds a bunch of other stuff" behavior is > generally a bad idea for any sort of lower level tool like Moose. This > is best reserved for highly opinionated things like corporate-internal > pragmas or a higher-level framework.
BTW, you can ā€˜{ use Moose; }ā€™ if you need to.


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.