Bug #69207 for Moose: Automatically import namespace::autoclean

Thu Jun 30 15:16:53 2011 DOHERTY [...] cpan.org - Ticket created

Subject:

Automatically import namespace::autoclean

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

Fri Feb 08 01:16:44 2013 ether [...] cpan.org - Correspondence added

We can't consider this until after MooseX::WithOverloading is cored.

Fri Feb 08 01:16:46 2013 The RT System itself - Status changed from 'new' to 'open'

Wed Mar 13 17:06:25 2013 ether [...] cpan.org - Severity Wishlist added

Sun Sep 11 14:32:32 2016 DROLSKY [...] cpan.org - Correspondence added

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.

Sun Sep 11 21:30:24 2016 $_ = 'spro^^*%*^6ut# [...] &$%*c>#!^!#&!pan.org'; y/a-z.@//cd; print - Correspondence added

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.