8 our $VERSION = '1.002000'; # 1.2.0
9 $VERSION = eval $VERSION;
11 require Moo::sification;
15 sub _install_tracked {
16 my ($target, $name, $code) = @_;
17 $MAKERS{$target}{exports}{$name} = $code;
18 _install_coderef "${target}::${name}" => "Moo::${name}" => $code;
25 if ($Moo::Role::INFO{$target} and $Moo::Role::INFO{$target}{is_role}) {
26 die "Cannot import Moo into a role";
28 $MAKERS{$target} ||= {};
29 _install_tracked $target => extends => sub {
30 $class->_set_superclasses($target, @_);
31 $class->_maybe_reset_handlemoose($target);
34 _install_tracked $target => with => sub {
36 Moo::Role->apply_roles_to_package($target, @_);
37 $class->_maybe_reset_handlemoose($target);
39 _install_tracked $target => has => sub {
40 my ($name_proto, %spec) = @_;
41 my $name_isref = ref $name_proto eq 'ARRAY';
42 foreach my $name ($name_isref ? @$name_proto : $name_proto) {
43 # Note that when $name_proto is an arrayref, each attribute
44 # needs a separate \%specs hashref
45 my $spec_ref = $name_isref ? +{%spec} : \%spec;
46 $class->_constructor_maker_for($target)
47 ->register_attribute_specs($name, $spec_ref);
48 $class->_accessor_maker_for($target)
49 ->generate_method($target, $name, $spec_ref);
50 $class->_maybe_reset_handlemoose($target);
54 foreach my $type (qw(before after around)) {
55 _install_tracked $target => $type => sub {
56 require Class::Method::Modifiers;
57 _install_modifier($target, $type, @_);
61 return if $MAKERS{$target}{is_class}; # already exported into this package
62 $MAKERS{$target}{is_class} = 1;
65 @{"${target}::ISA"} = do {
66 require Moo::Object; ('Moo::Object');
67 } unless @{"${target}::ISA"};
69 if ($INC{'Moo/HandleMoose.pm'}) {
70 Moo::HandleMoose::inject_fake_metaclass_for($target);
76 _unimport_coderefs($target, $MAKERS{$target});
79 sub _set_superclasses {
82 foreach my $superclass (@_) {
83 _load_module($superclass);
84 if ($INC{"Role/Tiny.pm"} && $Role::Tiny::INFO{$superclass}) {
86 Carp::croak("Can't extend role '$superclass'");
89 # Can't do *{...} = \@_ or 5.10.0's mro.pm stops seeing @ISA
90 @{*{_getglob("${target}::ISA")}{ARRAY}} = @_;
91 if (my $old = delete $Moo::MAKERS{$target}{constructor}) {
92 delete _getstash($target)->{new};
93 Moo->_constructor_maker_for($target)
94 ->register_attribute_specs(%{$old->all_attribute_specs});
96 elsif (!$target->isa('Moo::Object')) {
97 Moo->_constructor_maker_for($target);
99 no warnings 'once'; # piss off. -- mst
100 $Moo::HandleMoose::MOUSE{$target} = [
101 grep defined, map Mouse::Util::find_meta($_), @_
102 ] if Mouse::Util->can('find_meta');
105 sub _maybe_reset_handlemoose {
106 my ($class, $target) = @_;
107 if ($INC{"Moo/HandleMoose.pm"}) {
108 Moo::HandleMoose::maybe_reinject_fake_metaclass_for($target);
112 sub _accessor_maker_for {
113 my ($class, $target) = @_;
114 return unless $MAKERS{$target};
115 $MAKERS{$target}{accessor} ||= do {
116 my $maker_class = do {
118 if (my $defer_target =
119 (Sub::Defer::defer_info($target->can('new'))||[])->[0]
121 my ($pkg) = ($defer_target =~ /^(.*)::[^:]+$/);
122 $MAKERS{$pkg} && $MAKERS{$pkg}{accessor};
129 require Method::Generate::Accessor;
130 'Method::Generate::Accessor'
137 sub _constructor_maker_for {
138 my ($class, $target) = @_;
139 return unless $MAKERS{$target};
140 $MAKERS{$target}{constructor} ||= do {
141 require Method::Generate::Constructor;
143 my ($moo_constructor, $con);
145 my $t_new = $target->can('new');
147 if ($t_new == Moo::Object->can('new')) {
148 $moo_constructor = 1;
149 } elsif (my $defer_target = (Sub::Defer::defer_info($t_new)||[])->[0]) {
150 my ($pkg) = ($defer_target =~ /^(.*)::[^:]+$/);
152 $moo_constructor = 1;
153 $con = $MAKERS{$pkg}{constructor};
157 $moo_constructor = 1; # no other constructor, make a Moo one
159 ($con ? ref($con) : 'Method::Generate::Constructor')
162 accessor_generator => $class->_accessor_maker_for($target),
163 construction_string => (
165 ? ($con ? $con->construction_string : undef)
166 : ('$class->'.$target.'::SUPER::new($class->can(q[FOREIGNBUILDARGS]) ? $class->FOREIGNBUILDARGS(@_) : @_)')
168 subconstructor_handler => (
169 ' if ($Moo::MAKERS{$class}) {'."\n"
170 .' '.$class.'->_constructor_maker_for($class,'.perlstring($target).');'."\n"
171 .' return $class->new(@_)'.";\n"
172 .' } elsif ($INC{"Moose.pm"} and my $meta = Class::MOP::get_metaclass_by_name($class)) {'."\n"
173 .' return $meta->new_object($class->BUILDARGS(@_));'."\n"
178 ->register_attribute_specs(%{$con?$con->all_attribute_specs:{}})
189 Moo - Minimalist Object Orientation (with Moose compatibility)
199 my $amount = shift || 1;
201 $self->pounds( $self->pounds - $amount );
211 die "Only SWEET-TREATZ supported!" unless $_[0] eq 'SWEET-TREATZ'
217 isa => sub { die "$_[0] is too much cat food!" unless $_[0] < 15 },
224 my $full = Cat::Food->new(
225 taste => 'DELICIOUS.',
226 brand => 'SWEET-TREATZ',
236 This module is an extremely light-weight subset of L<Moose> optimised for
237 rapid startup and "pay only for what you use".
239 It also avoids depending on any XS modules to allow simple deployments. The
240 name C<Moo> is based on the idea that it provides almost -- but not quite -- two
243 Unlike L<Mouse> this module does not aim at full compatibility with
244 L<Moose>'s surface syntax, preferring instead of provide full interoperability
245 via the metaclass inflation capabilities described in L</MOO AND MOOSE>.
247 For a full list of the minor differences between L<Moose> and L<Moo>'s surface
248 syntax, see L</INCOMPATIBILITIES WITH MOOSE>.
250 =head1 WHY MOO EXISTS
252 If you want a full object system with a rich Metaprotocol, L<Moose> is
255 However, sometimes you're writing a command line script or a CGI script
256 where fast startup is essential, or code designed to be deployed as a single
257 file via L<App::FatPacker>, or you're writing a CPAN module and you want it
258 to be usable by people with those constraints.
260 I've tried several times to use L<Mouse> but it's 3x the size of Moo and
261 takes longer to load than most of my Moo based CGI scripts take to run.
263 If you don't want L<Moose>, you don't want "less metaprotocol" like L<Mouse>,
264 you want "as little as possible" -- which means "no metaprotocol", which is
267 Better still, if you install and load L<Moose>, we set up metaclasses for your
268 L<Moo> classes and L<Moo::Role> roles, so you can use them in L<Moose> code
269 without ever noticing that some of your codebase is using L<Moo>.
271 Hence, Moo exists as its name -- Minimal Object Orientation -- with a pledge
272 to make it smooth to upgrade to L<Moose> when you need more than minimal
277 If L<Moo> detects L<Moose> being loaded, it will automatically register
278 metaclasses for your L<Moo> and L<Moo::Role> packages, so you should be able
279 to use them in L<Moose> code without anybody ever noticing you aren't using
282 L<Moo> will also create L<Moose type constraints|Moose::Manual::Types> for
283 classes and roles, so that C<< isa => 'MyClass' >> and C<< isa => 'MyRole' >>
284 work the same as for L<Moose> classes and roles.
286 Extending a L<Moose> class or consuming a L<Moose::Role> will also work.
288 So will extending a L<Mouse> class or consuming a L<Mouse::Role> - but note
289 that we don't provide L<Mouse> metaclasses or metaroles so the other way
290 around doesn't work. This feature exists for L<Any::Moose> users porting to
291 L<Moo>; enabling L<Mouse> users to use L<Moo> classes is not a priority for us.
293 This means that there is no need for anything like L<Any::Moose> for Moo
294 code - Moo and Moose code should simply interoperate without problem. To
295 handle L<Mouse> code, you'll likely need an empty Moo role or class consuming
296 or extending the L<Mouse> stuff since it doesn't register true L<Moose>
297 metaclasses like L<Moo> does.
299 If you want types to be upgraded to the L<Moose> types, use
300 L<MooX::Types::MooseLike> and install the L<MooseX::Types> library to
301 match the L<MooX::Types::MooseLike> library you're using - L<Moo> will
302 load the L<MooseX::Types> library and use that type for the newly created
305 If you need to disable the metaclass creation, add:
309 to your code before Moose is loaded, but bear in mind that this switch is
310 currently global and turns the mechanism off entirely so don't put this
313 =head1 MOO VERSUS ANY::MOOSE
315 L<Any::Moose> will load L<Mouse> normally, and L<Moose> in a program using
316 L<Moose> - which theoretically allows you to get the startup time of L<Mouse>
317 without disadvantaging L<Moose> users.
319 Sadly, this doesn't entirely work, since the selection is load order dependent
320 - L<Moo>'s metaclass inflation system explained above in L</MOO AND MOOSE> is
321 significantly more reliable.
323 So if you want to write a CPAN module that loads fast or has only pure perl
324 dependencies but is also fully usable by L<Moose> users, you should be using
327 For a full explanation, see the article
328 L<http://shadow.cat/blog/matt-s-trout/moo-versus-any-moose> which explains
329 the differing strategies in more detail and provides a direct example of
330 where L<Moo> succeeds and L<Any::Moose> fails.
332 =head1 IMPORTED METHODS
336 Foo::Bar->new( attr1 => 3 );
340 Foo::Bar->new({ attr1 => 3 });
345 my ( $class, @args ) = @_;
347 unshift @args, "attr1" if @args % 2 == 1;
354 The default implementation of this method accepts a hash or hash reference of
355 named parameters. If it receives a single argument that isn't a hash reference
358 You can override this method in your class to handle other types of options
359 passed to the constructor.
361 This method should always return a hash reference of named options.
363 =head2 FOREIGNBUILDARGS
365 If you are inheriting from a non-Moo class, the arguments passed to the parent
366 class constructor can be manipulated by defining a C<FOREIGNBUILDARGS> method.
367 It will receive the same arguments as C<BUILDARGS>, and should return a list
368 of arguments to pass to the parent class constructor.
372 Define a C<BUILD> method on your class and the constructor will automatically
373 call the C<BUILD> method from parent down to child after the object has
374 been instantiated. Typically this is used for object validation or possibly
379 If you have a C<DEMOLISH> method anywhere in your inheritance hierarchy,
380 a C<DESTROY> method is created on first object construction which will call
381 C<< $instance->DEMOLISH($in_global_destruction) >> for each C<DEMOLISH>
382 method from child upwards to parents.
384 Note that the C<DESTROY> method is created on first construction of an object
385 of your class in order to not add overhead to classes without C<DEMOLISH>
386 methods; this may prove slightly surprising if you try and define your own.
390 if ($foo->does('Some::Role1')) {
394 Returns true if the object composes in the passed role.
396 =head1 IMPORTED SUBROUTINES
400 extends 'Parent::Class';
402 Declares base class. Multiple superclasses can be passed for multiple
403 inheritance (but please use roles instead).
405 Calling extends more than once will REPLACE your superclasses, not add to
406 them like 'use base' would.
414 with 'Some::Role1', 'Some::Role2';
416 Composes one or more L<Moo::Role> (or L<Role::Tiny>) roles into the current
417 class. An error will be raised if these roles have conflicting methods.
425 Declares an attribute for the class.
437 default => sub { "blah" },
440 Using the C<+> notation, it's possible to override an attribute.
442 The options for C<has> are as follows:
448 B<required>, may be C<ro>, C<lazy>, C<rwp> or C<rw>.
450 C<ro> generates an accessor that dies if you attempt to write to it - i.e.
451 a getter only - by defaulting C<reader> to the name of the attribute.
453 C<lazy> generates a reader like C<ro>, but also sets C<lazy> to 1 and
454 C<builder> to C<_build_${attribute_name}> to allow on-demand generated
455 attributes. This feature was my attempt to fix my incompetence when
456 originally designing C<lazy_build>, and is also implemented by
457 L<MooseX::AttributeShortcuts>. There is, however, nothing to stop you
458 using C<lazy> and C<builder> yourself with C<rwp> or C<rw> - it's just that
459 this isn't generally a good idea so we don't provide a shortcut for it.
461 C<rwp> generates a reader like C<ro>, but also sets C<writer> to
462 C<_set_${attribute_name}> for attributes that are designed to be written
463 from inside of the class, but read-only from outside.
464 This feature comes from L<MooseX::AttributeShortcuts>.
466 C<rw> generates a normal getter/setter by defaulting C<accessor> to the
467 name of the attribute.
471 Takes a coderef which is meant to validate the attribute. Unlike L<Moose>, Moo
472 does not include a basic type system, so instead of doing C<< isa => 'Num' >>,
476 die "$_[0] is not a number!" unless looks_like_number $_[0]
479 Note that the return value is ignored, only whether the sub lives or
482 L<Sub::Quote aware|/SUB QUOTE AWARE>
484 Since L<Moo> does B<not> run the C<isa> check before C<coerce> if a coercion
485 subroutine has been supplied, C<isa> checks are not structural to your code
486 and can, if desired, be omitted on non-debug builds (although if this results
487 in an uncaught bug causing your program to break, the L<Moo> authors guarantee
488 nothing except that you get to keep both halves).
490 If you want L<MooseX::Types> style named types, look at
491 L<MooX::Types::MooseLike>.
493 To cause your C<isa> entries to be automatically mapped to named
494 L<Moose::Meta::TypeConstraint> objects (rather than the default behaviour
495 of creating an anonymous type), set:
497 $Moo::HandleMoose::TYPE_MAP{$isa_coderef} = sub {
498 require MooseX::Types::Something;
499 return MooseX::Types::Something::TypeName();
502 Note that this example is purely illustrative; anything that returns a
503 L<Moose::Meta::TypeConstraint> object or something similar enough to it to
504 make L<Moose> happy is fine.
508 Takes a coderef which is meant to coerce the attribute. The basic idea is to
509 do something like the following:
512 $_[0] + 1 unless $_[0] % 2
515 Note that L<Moo> will always fire your coercion: this is to permit
516 C<isa> entries to be used purely for bug trapping, whereas coercions are
517 always structural to your code. We do, however, apply any supplied C<isa>
518 check after the coercion has run to ensure that it returned a valid value.
520 L<Sub::Quote aware|/SUB QUOTE AWARE>
526 handles => 'RobotRole'
528 Where C<RobotRole> is a role (L<Moo::Role>) that defines an interface which
529 becomes the list of methods to handle.
531 Takes a list of methods
533 handles => [ qw( one two ) ]
543 Takes a coderef which will get called any time the attribute is set. This
544 includes the constructor, but not default or built values. Coderef will be
545 invoked against the object with the new value as an argument.
547 If you set this to just C<1>, it generates a trigger which calls the
548 C<_trigger_${attr_name}> method on C<$self>. This feature comes from
549 L<MooseX::AttributeShortcuts>.
551 Note that Moose also passes the old value, if any; this feature is not yet
554 L<Sub::Quote aware|/SUB QUOTE AWARE>
558 Takes a coderef which will get called with $self as its only argument
559 to populate an attribute if no value is supplied to the constructor - or
560 if the attribute is lazy, when the attribute is first retrieved if no
561 value has yet been provided.
563 If a simple scalar is provided, it will be inlined as a string. Any non-code
564 reference (hash, array) will result in an error - for that case instead use
565 a code reference that returns the desired value.
567 Note that if your default is fired during new() there is no guarantee that
568 other attributes have been populated yet so you should not rely on their
571 L<Sub::Quote aware|/SUB QUOTE AWARE>
575 Takes a method name which will return true if an attribute has a value.
577 If you set this to just C<1>, the predicate is automatically named
578 C<has_${attr_name}> if your attribute's name does not start with an
579 underscore, or C<_has_${attr_name_without_the_underscore}> if it does.
580 This feature comes from L<MooseX::AttributeShortcuts>.
584 Takes a method name which will be called to create the attribute - functions
585 exactly like default except that instead of calling
593 The following features come from L<MooseX::AttributeShortcuts>:
595 If you set this to just C<1>, the builder is automatically named
596 C<_build_${attr_name}>.
598 If you set this to a coderef or code-convertible object, that variable will be
599 installed under C<$class::_build_${attr_name}> and the builder set to the same
604 Takes a method name which will clear the attribute.
606 If you set this to just C<1>, the clearer is automatically named
607 C<clear_${attr_name}> if your attribute's name does not start with an
608 underscore, or <_clear_${attr_name_without_the_underscore}> if it does.
609 This feature comes from L<MooseX::AttributeShortcuts>.
613 B<Boolean>. Set this if you want values for the attribute to be grabbed
614 lazily. This is usually a good idea if you have a L</builder> which requires
615 another attribute to be set.
619 B<Boolean>. Set this if the attribute must be passed on instantiation.
623 The value of this attribute will be the name of the method to get the value of
624 the attribute. If you like Java style methods, you might set this to
629 The value of this attribute will be the name of the method to set the value of
630 the attribute. If you like Java style methods, you might set this to
635 B<Boolean>. Set this if you want the reference that the attribute contains to
636 be weakened; use this when circular references are possible, which will cause
641 Takes the name of the key to look for at instantiation time of the object. A
642 common use of this is to make an underscored attribute have a non-underscored
643 initialization name. C<undef> means that passing the value in on instantiation
648 Takes either a coderef or array of coderefs which is meant to transform the
649 given attributes specifications if necessary when upgrading to a Moose role or
650 class. You shouldn't need this by default, but is provided as a means of
651 possible extensibility.
657 before foo => sub { ... };
659 See L<< Class::Method::Modifiers/before method(s) => sub { ... } >> for full
664 around foo => sub { ... };
666 See L<< Class::Method::Modifiers/around method(s) => sub { ... } >> for full
671 after foo => sub { ... };
673 See L<< Class::Method::Modifiers/after method(s) => sub { ... } >> for full
676 =head1 SUB QUOTE AWARE
678 L<Sub::Quote/quote_sub> allows us to create coderefs that are "inlineable,"
679 giving us a handy, XS-free speed boost. Any option that is L<Sub::Quote>
680 aware can take advantage of this.
682 To do this, you can write
689 isa => quote_sub(q{ die "Not <3" unless $_[0] < 3 })
692 which will be inlined as
695 local @_ = ($_[0]->{foo});
696 die "Not <3" unless $_[0] < 3;
699 or to avoid localizing @_,
703 isa => quote_sub(q{ my ($val) = @_; die "Not <3" unless $val < 3 })
706 which will be inlined as
709 my ($val) = ($_[0]->{foo});
710 die "Not <3" unless $val < 3;
713 See L<Sub::Quote> for more information, including how to pass lexical
714 captures that will also be compiled into the subroutine.
716 =head1 INCOMPATIBILITIES WITH MOOSE
718 There is no built-in type system. C<isa> is verified with a coderef; if you
719 need complex types, just make a library of coderefs, or better yet, functions
720 that return quoted subs. L<MooX::Types::MooseLike> provides a similar API
721 to L<MooseX::Types::Moose> so that you can write
723 has days_to_live => (is => 'ro', isa => Int);
725 and have it work with both; it is hoped that providing only subrefs as an
726 API will encourage the use of other type systems as well, since it's
727 probably the weakest part of Moose design-wise.
729 C<initializer> is not supported in core since the author considers it to be a
730 bad idea and Moose best practices recommend avoiding it. Meanwhile C<trigger> or
731 C<coerce> are more likely to be able to fulfill your needs.
733 There is no meta object. If you need this level of complexity you wanted
734 L<Moose> - Moo succeeds at being small because it explicitly does not
735 provide a metaprotocol. However, if you load L<Moose>, then
737 Class::MOP::class_of($moo_class_or_role)
739 will return an appropriate metaclass pre-populated by L<Moo>.
741 No support for C<super>, C<override>, C<inner>, or C<augment> - the author
742 considers augment to be a bad idea, and override can be translated:
744 override foo => sub {
751 my ($orig, $self) = (shift, shift);
757 The C<dump> method is not provided by default. The author suggests loading
758 L<Devel::Dwarn> into C<main::> (via C<perl -MDevel::Dwarn ...> for example) and
759 using C<$obj-E<gt>$::Dwarn()> instead.
761 L</default> only supports coderefs and plain scalars, because passing a hash
762 or array reference as a default is almost always incorrect since the value is
763 then shared between all objects using that default.
765 C<lazy_build> is not supported; you are instead encouraged to use the
766 C<< is => 'lazy' >> option supported by L<Moo> and L<MooseX::AttributeShortcuts>.
768 C<auto_deref> is not supported since the author considers it a bad idea and
769 it has been considered best practice to avoid it for some time.
771 C<documentation> will show up in a L<Moose> metaclass created from your class
772 but is otherwise ignored. Then again, L<Moose> ignores it as well, so this
773 is arguably not an incompatibility.
775 Since C<coerce> does not require C<isa> to be defined but L<Moose> does
776 require it, the metaclass inflation for coerce alone is a trifle insane
777 and if you attempt to subtype the result will almost certainly break.
779 Handling of warnings: when you C<use Moo> we enable FATAL warnings. The nearest
780 similar invocation for L<Moose> would be:
783 use warnings FATAL => "all";
785 Additionally, L<Moo> supports a set of attribute option shortcuts intended to
786 reduce common boilerplate. The set of shortcuts is the same as in the L<Moose>
787 module L<MooseX::AttributeShortcuts> as of its version 0.009+. So if you:
792 The nearest L<Moose> invocation would be:
797 use warnings FATAL => "all";
798 use MooseX::AttributeShortcuts;
800 or, if you're inheriting from a non-Moose class,
805 use MooseX::NonMoose;
806 use warnings FATAL => "all";
807 use MooseX::AttributeShortcuts;
809 Finally, Moose requires you to call
811 __PACKAGE__->meta->make_immutable;
813 at the end of your class to get an inlined (i.e. not horribly slow)
814 constructor. Moo does it automatically the first time ->new is called
815 on your class. (C<make_immutable> is a no-op in Moo to ease migration.)
817 An extension L<MooX::late> exists to ease translating Moose packages
818 to Moo by providing a more Moose-like interface.
822 Users' IRC: #moose on irc.perl.org
824 =for html <a href="http://chat.mibbit.com/#moose@irc.perl.org">(click for instant chatroom login)</a>
826 Development and contribution IRC: #web-simple on irc.perl.org
828 =for html <a href="http://chat.mibbit.com/#web-simple@irc.perl.org">(click for instant chatroom login)</a>
830 Bugtracker: L<http://rt.cpan.org/NoAuth/Bugs.html?Dist=Moo>
832 Git repository: L<git://git.shadowcat.co.uk/gitmo/Moo.git>
834 Git web access: L<http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=gitmo/Moo.git>
838 mst - Matt S. Trout (cpan:MSTROUT) <mst@shadowcat.co.uk>
842 dg - David Leadbeater (cpan:DGL) <dgl@dgl.cx>
844 frew - Arthur Axel "fREW" Schmidt (cpan:FREW) <frioux@gmail.com>
846 hobbs - Andrew Rodland (cpan:ARODLAND) <arodland@cpan.org>
848 jnap - John Napiorkowski (cpan:JJNAPIORK) <jjn1056@yahoo.com>
850 ribasushi - Peter Rabbitson (cpan:RIBASUSHI) <ribasushi@cpan.org>
852 chip - Chip Salzenberg (cpan:CHIPS) <chip@pobox.com>
854 ajgb - Alex J. G. Burzyński (cpan:AJGB) <ajgb@cpan.org>
856 doy - Jesse Luehrs (cpan:DOY) <doy at tozt dot net>
858 perigrin - Chris Prather (cpan:PERIGRIN) <chris@prather.org>
860 Mithaldu - Christian Walde (cpan:MITHALDU) <walde.christian@googlemail.com>
862 ilmari - Dagfinn Ilmari Mannsåker (cpan:ILMARI) <ilmari@ilmari.org>
864 tobyink - Toby Inkster (cpan:TOBYINK) <tobyink@cpan.org>
866 haarg - Graham Knop (cpan:HAARG) <haarg@cpan.org>
868 mattp - Matt Phillips (cpan:MATTP) <mattp@cpan.org>
872 Copyright (c) 2010-2011 the Moo L</AUTHOR> and L</CONTRIBUTORS>
877 This library is free software and may be distributed under the same terms
878 as perl itself. See L<http://dev.perl.org/licenses/>.