Sure, I was more commenting on the trade off as an aside and why it isn't
in Moose core.
-Chris
On Monday, May 20, 2013, Darren Duncan wrote:
> If that was just done as part of a test suite though, and not in
> production, the performance hit might be worth it. -- Darren Duncan
>
> On 2013.05.20
If that was just done as part of a test suite though, and not in production, the
performance hit might be worth it. -- Darren Duncan
On 2013.05.20 3:07 PM, Chris Prather wrote:
Using the hashref directly totally circumvents moose. You would need to write
something like MooseX::Globref that rep
Using the hashref directly totally circumvents moose. You would need to write
something like MooseX::Globref that replaces the instance type with a
restricted hash. This would seriously impact performance.
-Chris
—
Sent from Mailbox for iPhone
On Mon, May 20, 2013 at 5:55 PM, Sam Brain wrote
I have a simple application which uses Moose (example copied from
Moose::Manual::MooseX pages)
package User;
use Moose;
use MooseX::StrictConstructor;
use namespace::autoclean;
has 'name' => (is => 'rw', isa => 'Str');
has 'email' => (is => 'rw', isa => 'Str');
package main;
my $bob = User-
