Skip Menu |

This queue is for tickets about the Moose CPAN distribution.

Report information
The Basics
Id: 64731
Status: open
Priority: 0/
Queue: Moose
People
Owner: Nobody in particular
Requestors: mschwern [...] cpan.org
Cc:
AdminCc:
Bug Information
Severity: Wishlist
Broken in: 1.21
Fixed in: (no value)

History Show all quoted text
  Thu Jan 13 02:07:24 2011 mschwern [...] cpan.org - Ticket created
Subject: Warn when you subclass from a non-Moose class
Mouse has a very nice feature that warns you if you inherit from a non-Mouse class. This has saved me a lot of hair pulling trying to figure out why things are silently not working. Silent errors are bad. I would like to see Moose issue a similar warning. As it would be rude to issue a warning and then provide no solution, Moose would embrace the functionality of MooseX::NonMoose. It would also provide a Moose::NoIReallyMeanToInheritFromNonMooseAndDontTryToFixIt module. Arguments for/against the warning are here: https://rt.cpan.org/Ticket/Display.html?id=63675
  Thu Jan 13 10:33:23 2011 stevan.little [...] gmail.com - Correspondence added
Subject: Re: [rt.cpan.org #64731] Warn when you subclass from a non-Moose class
Date: Thu, 13 Jan 2011 10:33:15 -0500
To: bug-Moose [...] rt.cpan.org
From: Stevan Little <stevan.little [...] iinteractive.com>
I agree. We have talked about coring MX::NonMoose before. I think that should be part of the upcoming 2.0 On Jan 13, 2011 2:07 AM, "Michael G Schwern via RT" <bug-Moose@rt.cpan.org> wrote: Show quoted text
> Thu Jan 13 02:07:24 2011: Request 64731 was acted upon. > Transaction: Ticket created by MSCHWERN > Queue: Moose > Subject: Warn when you subclass from a non-Moose class > Broken in: 1.21 > Severity: Wishlist > Owner: Nobody > Requestors: mschwern@cpan.org > Status: new > Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=64731 > > > > Mouse has a very nice feature that warns you if you inherit from a > non-Mouse class. This has saved me a lot of hair pulling trying to > figure out why things are silently not working. Silent errors are bad. > > I would like to see Moose issue a similar warning. > > As it would be rude to issue a warning and then provide no solution, > Moose would embrace the functionality of MooseX::NonMoose. It would > also provide a > Moose::NoIReallyMeanToInheritFromNonMooseAndDontTryToFixIt module. > > Arguments for/against the warning are here: > https://rt.cpan.org/Ticket/Display.html?id=63675 >
  Thu Jan 13 10:33:24 2011 The RT System itself - Status changed from 'new' to 'open'