Re: A branch to review: topic/strict-constructor

2010-03-03 Thread Christopher Brown
I have to agree with the above assessment. Tying 'strict' and 'immutability' doesn't make sense. They are orthogonal concepts. And, I am not a fan of Moose::Strict either. Yet another packages to remember, separate documentation. If you fork into use Moose and use Moose::Strict, someone will

Re: Problem with use Moose -strict

2010-03-03 Thread Nick Perez
On Wed, 3 Mar 2010 13:20:06 -0600 (CST) Dave Rolsky auta...@urth.org wrote: So with that in mind, maybe the flag needs to be more specific, like -strict-constructor. We could also offer a catchall -all-strict-i-mean-it flag (with a better name) that would be explicitly documented as

Re: Problem with use Moose -strict

2010-03-03 Thread Goro Fuji
On 4 March 2010 04:20, Dave Rolsky auta...@urth.org wrote: I like the interface, and I think it's preferable to a separate Moose::Strict module. However, the problem with naming the flag strict is the same problem Perl has with the strict pragma. Strict is a very general name, which we'd be