=pod =head1 NAME Moose::Cookbook::WTF - For when things go wrong with Moose =head1 COMMON PROBLEMS =head2 Speed =head3 Why is my code taking so long to load? Moose does have a compile time performance burden, which it inherits from Class::MOP. If load/compile time is a concern for your application, Moose may not be the right tool for you. Although, you should note that we are exploring the use of L to try and reduce this problem, but nothing is ready yet. =head3 Why are my objects taking so long to construct? Moose uses a lot of introspection when constructing an instance, and introspection can be slow. This problem can be solved by making your class immutable. This can be done with the following code: MyClass->meta->make_immutable(); Moose will then memoize a number of meta-level methods and inline a constructor for you. For more information on this see the L section below and in the L. =head2 Constructors & Immutability =head3 I made my class immutable, but C it is still slow! Do you have a custom C method in your class? Moose will not overwrite your custom C method, you would probably do better to try and convert this to use the C method or possibly set C values in the attribute declaration. =head3 I made my class immutable, and now my (before | after | around) C is not being called? Making a I, I or I wrap around the C method, will actually create a C method within your class. This will prevent Moose from creating one itself when you make the class immutable. =head2 Accessors =head3 I created an attribute, where are my accessors? Accessors are B created implicitly, you B ask Moose to create them for you. My guess is that you have this: has 'foo' => (isa => 'Bar'); when what you really want to say is: has 'foo' => (isa => 'Bar', is => 'rw'); The reason this is so, is because it is a perfectly valid use case to I have an accessor. The simplest one is that you want to write your own. If Moose created on automatically, then because of the order in which classes are constructed, Moose would overwrite your custom accessor. You wouldn't want that would you? =head2 Method Modfiers =head3 How come I can't change C<@_> in a C modifier? The C modifier simply is called I the main method. Its return values are simply ignored, and are B passed onto the main method body. There are a number of reasons for this, but those arguments are too lengthy for this document. Instead, I suggest using an C modifier instead. Here is some sample code: around 'foo' => sub { my $next = shift; my ($self, @args) = @_; # do something silly here to @args $next->($self, reverse(@args)); }; =head3 How come I can't see return values in an C modifier? As with the C modifier, the C modifier is simply called I the main method. It is passed the original contents of C<@_> and B the return values of the main method. Again, the arguments are too lengthy as to why this has to be. And as with C I recommend using an C modifier instead. Here is some sample code: around 'foo' => sub { my $next = shift; my ($self, @args) = @_; my @rv = $next->($self, @args); # do something silly with the return values return reverse @rv; }; =head2 Moose and Attributes =head3 Why doesn't attributes I inherited from a superclass work? Currently when you subclass a module, this is done at runtime with the C keyword but attributes are checked at compile time by Perl. To make attributes work, you must place C in a C block so that the attribute handlers will be available at compile time like this: BEGIN { extends qw/Foo/ } =head2 Moose and Other Modules =head3 Why can't I get Catalyst and Moose to work together? See L. =head1 AUTHOR Stevan Little Estevan@iinteractive.comE Anders Nor Berle Edebolaz@gmail.comE =head1 COPYRIGHT AND LICENSE Copyright 2006, 2007 by Infinity Interactive, Inc. L This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself. =cut