1 package Moose::Manual::Delta;
3 # ABSTRACT: Important Changes in Moose
11 This documents any important or noteworthy changes in Moose, with a
12 focus on things that affect backwards compatibility. This does duplicate data
13 from the F<Changes> file, but aims to provide more details and when possible
16 Besides helping keep up with changes, you can also use this document
17 for finding the lowest version of Moose that supported a given
18 feature. If you encounter a problem and have a solution but don't see
19 it documented here, or think we missed an important feature, please
26 =item Hand-optimized type constraint code causes a deprecation warning
28 If you provide an optimized sub ref for a type constraint, this now causes a
29 deprecation warning. Typically, this comes from passing an C<optimize_as>
30 parameter to C<subtype>, but it could also happen if you create a
31 L<Moose::Meta::TypeConstraint> object directly.
33 Use the inlining feature (C<inline_as>) added in 2.0100 instead.
35 =item Array and Hash native traits provide a C<shallow_clone> method
37 The Array and Hash native traits now provide a "shallow_clone" method, which
38 will return a reference to a new container with the same contents as the
39 attribute's reference.
47 =item Hand-optimized type constraint code is deprecated in favor of inlining
49 Moose allows you to provide a hand-optimized version of a type constraint's
50 subroutine reference. This version allows type constraints to generate inline
51 code, and you should use this inlining instead of providing a hand-optimized
54 This affects the C<optimize_as> sub exported by
55 L<Moose::Util::TypeConstraints>. Use C<inline_as> instead.
57 This will start warning in the 2.0300 release.
63 =item More useful type constraint error messages
65 If you have L<Devel::PartialDump> version 0.14 or higher installed, Moose's
66 type constraint error messages will use it to display the invalid value, rather
67 than just displaying it directly. This will generally be much more useful. For
68 instance, instead of this:
70 Attribute (foo) does not pass the type constraint because: Validation failed for 'ArrayRef[Int]' with value ARRAY(0x275eed8)
72 the error message will instead look like
74 Attribute (foo) does not pass the type constraint because: Validation failed for 'ArrayRef[Int]' with value [ "a" ]
76 Note that L<Devel::PartialDump> can't be made a direct dependency at the
77 moment, because it uses Moose itself, but we're considering options to make
86 =item Roles have their own default attribute metaclass
88 Previously, when a role was applied to a class, it would use the attribute
89 metaclass defined in the class when copying over the attributes in the role.
90 This was wrong, because for instance, using L<MooseX::FollowPBP> in the class
91 would end up renaming all of the accessors generated by the role, some of which
92 may be being called in the role, causing it to break. Roles now keep track of
93 their own attribute metaclass to use by default when being applied to a class
94 (defaulting to Moose::Meta::Attribute). This is modifiable using
95 L<Moose::Util::MetaRole> by passing the C<applied_attribute> key to the
96 C<role_metaroles> option, as in:
98 Moose::Util::MetaRole::apply_metaroles(
101 attribute => ['My::Meta::Role::Attribute'],
104 applied_attribute => ['My::Meta::Role::Attribute'],
108 =item Class::MOP has been folded into the Moose dist
110 Moose and Class::MOP are tightly related enough that they have always had to be
111 kept pretty closely in step in terms of versions. Making them into a single
112 dist should simplify the upgrade process for users, as it should no longer be
113 possible to upgrade one without the other and potentially cause issues. No
114 functionality has changed, and this should be entirely transparent.
116 =item Moose's conflict checking is more robust and useful
118 There are two parts to this. The most useful one right now is that Moose will
119 ship with a C<moose-outdated> script, which can be run at any point to list the
120 modules which are installed that conflict with the installed version of Moose.
121 After upgrading Moose, running C<moose-outdated | cpanm> should be sufficient
122 to ensure that all of the Moose extensions you use will continue to work.
124 The other part is that Moose's C<META.json> file will also specify the
125 conflicts under the C<x_conflicts> key. We are working with the Perl tool chain
126 developers to try to get conflicts support added to CPAN clients, and if/when
127 that happens, the metadata already exists, and so the conflict checking will
130 =item Most deprecated APIs/features are slated for removal in Moose 2.0200
132 Most of the deprecated APIs and features in Moose will start throwing an error
133 in Moose 2.0200. Some of the features will go away entirely, and some will
134 simply throw an error.
136 The things on the chopping block are:
140 =item * Old public methods in Class::MOP and Moose
142 This includes things like C<< Class::MOP::Class->get_attribute_map >>, C<<
143 Class::MOP::Class->construct_instance >>, and many others. These were
144 deprecated in L<Class::MOP> 0.80_01, released on April 5, 2009.
146 These methods will be removed entirely in Moose 2.0200.
148 =item * Old public functions in Class::MOP
150 This include C<Class::MOP::subname>, C<Class::MOP::in_global_destruction>, and
151 the C<Class::MOP::HAS_ISAREV> constant. The first two were deprecated in 0.84,
152 and the last in 0.80. Class::MOP 0.84 was released on May 12, 2009.
154 These functions will be removed entirely in Moose 2.0200.
156 =item * The C<alias> and C<excludes> option for role composition
158 These were renamed to C<-alias> and C<-excludes> in Moose 0.89, released on
161 Passing these will throw an error in Moose 2.0200.
163 =item * The old L<Moose::Util::MetaRole> API
165 This include the C<apply_metaclass_roles()> function, as well as passing the
166 C<for_class> or any key ending in C<_roles> to C<apply_metaroles()>. This was
167 deprecated in Moose 0.93_01, released on January 4, 2010.
169 These will all throw an error in Moose 2.0200.
171 =item * Passing plain lists to C<type()> or C<subtype()>
173 The old API for these functions allowed you to pass a plain list of parameter,
174 rather than a list of hash references (which is what C<as()>, C<where>,
175 etc. return). This was deprecated in Moose 0.71_01, released on February 22,
178 This will throw an error in Moose 2.0200.
180 =item * The Role subtype
182 This subtype was deprecated in Moose 0.84, released on June 26, 2009.
184 This will be removed entirely in Moose 2.0200.
194 =item * New release policy
196 As of the 2.0 release, Moose now has an official release and support policy,
197 documented in L<Moose::Manual::Support>. All API changes will now go through a
198 deprecation cycle of at least one year, after which the deprecated API can be
199 removed. Deprecations and removals will only happen in major releases.
201 In between major releases, we will still make minor releases to add new
202 features, fix bugs, update documentation, etc.
210 =item Configurable stacktraces
212 Classes which use the L<Moose::Error::Default> error class can now have
213 stacktraces disabled by setting the C<MOOSE_ERROR_STYLE> env var to C<croak>.
214 This is experimental, fairly incomplete, and won't work in all cases (because
215 Moose's error system in general is all of these things), but this should allow
216 for reducing at least some of the verbosity in most cases.
224 =item Native Delegations
226 In previous versions of Moose, the Native delegations were created as
227 closures. The generated code was often quite slow compared to doing the same
228 thing by hand. For example, the Array's push delegation ended up doing
231 push @{ $self->$reader() }, @_;
233 If the attribute was created without a reader, the C<$reader> sub reference
234 followed a very slow code path. Even with a reader, this is still slower than
237 Native delegations are now generated as inline code, just like other
238 accessors, so we can access the slot directly.
240 In addition, native traits now do proper constraint checking in all cases. In
241 particular, constraint checking has been improved for array and hash
242 references. Previously, only the I<contained> type (the C<Str> in
243 C<HashRef[Str]>) would be checked when a new value was added to the
244 collection. However, if there was a constraint that applied to the whole
245 value, this was never checked.
247 In addition, coercions are now called on the whole value.
249 The delegation methods now do more argument checking. All of the methods check
250 that a valid number of arguments were passed to the method. In addition, the
251 delegation methods check that the arguments are sane (array indexes, hash
252 keys, numbers, etc.) when applicable. We have tried to emulate the behavior of
253 Perl builtins as much as possible.
255 Finally, triggers are called whenever the value of the attribute is changed by
258 These changes are only likely to break code in a few cases.
260 The inlining code may or may not preserve the original reference when changes
261 are made. In some cases, methods which change the value may replace it
262 entirely. This will break tied values.
264 If you have a typed arrayref or hashref attribute where the type enforces a
265 constraint on the whole collection, this constraint will now be checked. It's
266 possible that code which previously ran without errors will now cause the
267 constraint to fail. However, presumably this is a good thing ;)
269 If you are passing invalid arguments to a delegation which were previously
270 being ignored, these calls will now fail.
272 If your code relied on the trigger only being called for a regular writer,
273 that may cause problems.
275 As always, you are encouraged to test before deploying the latest version of
278 =item Defaults is and default for String, Counter, and Bool
280 A few native traits (String, Counter, Bool) provide default values of "is" and
281 "default" when you created an attribute. Allowing them to provide these values
282 is now deprecated. Supply the value yourself when creating the attribute.
284 =item The C<meta> method
286 Moose and Class::MOP have been cleaned up internally enough to make the
287 C<meta> method that you get by default optional. C<use Moose> and
288 C<use Moose::Role> now can take an additional C<-meta_name> option, which
289 tells Moose what name to use when installing the C<meta> method. Passing
290 C<undef> to this option suppresses generation of the C<meta> method
291 entirely. This should be useful for users of modules which also use a C<meta>
292 method or function, such as L<Curses> or L<Rose::DB::Object>.
300 =item All deprecated features now warn
302 Previously, deprecation mostly consisted of simply saying "X is deprecated" in
303 the Changes file. We were not very consistent about actually warning. Now, all
304 deprecated features still present in Moose actually give a warning. The
305 warning is issued once per calling package. See L<Moose::Deprecated> for more
308 =item You cannot pass C<< coerce => 1 >> unless the attribute's type constraint has a coercion
310 Previously, this was accepted, and it sort of worked, except that if you
311 attempted to set the attribute after the object was created, you would get a
314 Now you will get a warning when you attempt to define the attribute.
316 =item C<no Moose>, C<no Moose::Role>, and C<no Moose::Exporter> no longer unimport strict and warnings
318 This change was made in 1.05, and has now been reverted. We don't know if the
319 user has explicitly loaded strict or warnings on their own, and unimporting
320 them is just broken in that case.
322 =item Reversed logic when defining which options can be changed
324 L<Moose::Meta::Attribute> now allows all options to be changed in an
325 overridden attribute. The previous behaviour required each option to be
326 whitelisted using the C<legal_options_for_inheritance> method. This method has
327 been removed, and there is a new method, C<illegal_options_for_inheritance>,
328 which can now be used to prevent certain options from being changeable.
330 In addition, we only throw an error if the illegal option is actually
331 changed. If the superclass didn't specify this option at all when defining the
332 attribute, the subclass version can still add it as an option.
334 Example of overriding this in an attribute trait:
336 package Bar::Meta::Attribute;
339 has 'my_illegal_option' => (
344 around illegal_options_for_inheritance => sub {
345 return ( shift->(@_), qw/my_illegal_option/ );
354 =item L<Moose::Object/BUILD> methods are now called when calling C<new_object>
356 Previously, C<BUILD> methods would only be called from C<Moose::Object::new>,
357 but now they are also called when constructing an object via
358 C<Moose::Meta::Class::new_object>. C<BUILD> methods are an inherent part of the
359 object construction process, and this should make C<< $meta->new_object >>
360 actually usable without forcing people to use C<< $meta->name->new >>.
362 =item C<no Moose>, C<no Moose::Role>, and C<no Moose::Exporter> now unimport strict and warnings
364 In the interest of having C<no Moose> clean up everything that C<use Moose>
365 does in the calling scope, C<no Moose> (as well as all other
366 L<Moose::Exporter>-using modules) now unimports strict and warnings.
368 =item Metaclass compatibility checking and fixing should be much more robust
370 The L<metaclass compatibility|Moose/METACLASS COMPATIBILITY AND MOOSE> checking
371 and fixing algorithms have been completely rewritten, in both Class::MOP and
372 Moose. This should resolve many confusing errors when dealing with non-Moose
373 inheritance and with custom metaclasses for things like attributes,
374 constructors, etc. For correct code, the only thing that should require a
375 change is that custom error metaclasses must now inherit from
376 L<Moose::Error::Default>.
384 =item Moose::Meta::TypeConstraint::Class is_subtype_of behavior
386 Earlier versions of L<is_subtype_of|Moose::Meta::TypeConstraint::Class/is_subtype_of>
387 would incorrectly return true when called with itself, its own TC name or
388 its class name as an argument. (i.e. $foo_tc->is_subtype_of('Foo') == 1) This
389 behavior was a caused by C<isa> being checked before the class name. The old
390 behavior can be accessed with L<is_type_of|Moose::Meta::TypeConstraint::Class/is_type_of>
398 =item Moose::Meta::Attribute::Native::Trait::Code no longer creates reader methods by default
400 Earlier versions of L<Moose::Meta::Attribute::Native::Trait::Code> created
401 read-only accessors for the attributes it's been applied to, even if you didn't
402 ask for it with C<< is => 'ro' >>. This incorrect behaviour has now been fixed.
410 =item Moose::Util add_method_modifier behavior
412 add_method_modifier (and subsequently the sugar functions Moose::before,
413 Moose::after, and Moose::around) can now accept arrayrefs, with the same
414 behavior as lists. Types other than arrayref and regexp result in an error.
418 =head1 0.93_01 and 0.94
422 =item Moose::Util::MetaRole API has changed
424 The C<apply_metaclass_roles> function is now called C<apply_metaroles>. The
425 way arguments are supplied has been changed to force you to distinguish
426 between metaroles applied to L<Moose::Meta::Class> (and helpers) versus
427 L<Moose::Meta::Role>.
429 The old API still works, but will warn in a future release, and eventually be
432 =item Moose::Meta::Role has real attributes
434 The attributes returned by L<Moose::Meta::Role> are now instances of the
435 L<Moose::Meta::Role::Attribute> class, instead of bare hash references.
437 =item "no Moose" now removes C<blessed> and C<confess>
439 Moose is now smart enough to know exactly what it exported, even when it
440 re-exports functions from other packages. When you unimport Moose, it will
441 remove these functions from your namespace unless you I<also> imported them
442 directly from their respective packages.
444 If you have a C<no Moose> in your code I<before> you call C<blessed> or
445 C<confess>, your code will break. You can either move the C<no Moose> call
446 later in your code, or explicitly import the relevant functions from the
447 packages that provide them.
449 =item L<Moose::Exporter> is smarter about unimporting re-exports
451 The change above comes from a general improvement to L<Moose::Exporter>. It
452 will now unimport any function it exports, even if that function is a
453 re-export from another package.
455 =item Attributes in roles can no longer override class attributes with "+foo"
457 Previously, this worked more or less accidentally, because role attributes
458 weren't objects. This was never documented, but a few MooseX modules took
461 =item The composition_class_roles attribute in L<Moose::Meta::Role> is now a method
463 This was done to make it possible for roles to alter the the list of
464 composition class roles by applying a method modifiers. Previously, this was
465 an attribute and MooseX modules override it. Since that no longer works, this
468 This I<should> be an attribute, so this may switch back to being an attribute
469 in the future if we can figure out how to make this work.
477 =item Calling $object->new() is no longer deprecated
479 We decided to undeprecate this. Now it just works.
481 =item Both C<get_method_map> and C<get_attribute_map> is deprecated
483 These metaclass methods were never meant to be public, and they are both now
484 deprecated. The work around if you still need the functionality they provided
485 is to iterate over the list of names manually.
487 my %fields = map { $_ => $meta->get_attribute($_) } $meta->get_attribute_list;
489 This was actually a change in L<Class::MOP>, but this version of Moose
490 requires a version of L<Class::MOP> that includes said change.
498 =item Added Native delegation for Code refs
500 See L<Moose::Meta::Attribute::Native::Trait::Code> for details.
502 =item Calling $object->new() is deprecated
504 Moose has long supported this, but it's never really been documented, and we
505 don't think this is a good practice. If you want to construct an object from
506 an existing object, you should provide some sort of alternate constructor like
507 C<< $object->clone >>.
509 Calling C<< $object->new >> now issues a warning, and will be an error in a
512 =item Moose no longer warns if you call C<make_immutable> for a class with mutable ancestors
514 While in theory this is a good thing to warn about, we found so many
515 exceptions to this that doing this properly became quite problematic.
523 =item New Native delegation methods from L<List::Util> and L<List::MoreUtils>
525 In particular, we now have C<reduce>, C<shuffle>, C<uniq>, and C<natatime>.
527 =item The Moose::Exporter with_caller feature is now deprecated
529 Use C<with_meta> instead. The C<with_caller> option will start warning in a
532 =item Moose now warns if you call C<make_immutable> for a class with mutable ancestors
534 This is dangerous because modifying a class after a subclass has been
535 immutabilized will lead to incorrect results in the subclass, due to inlining,
536 caching, etc. This occasionally happens accidentally, when a class loads one
537 of its subclasses in the middle of its class definition, so pointing out that
538 this may cause issues should be helpful. Metaclasses (classes that inherit
539 from L<Class::MOP::Object>) are currently exempt from this check, since at the
540 moment we aren't very consistent about which metaclasses we immutabilize.
542 =item C<enum> and C<duck_type> now take arrayrefs for all forms
544 Previously, calling these functions with a list would take the first element of
545 the list as the type constraint name, and use the remainder as the enum values
546 or method names. This makes the interface inconsistent with the anon-type forms
547 of these functions (which must take an arrayref), and a free-form list where
548 the first value is sometimes special is hard to validate (and harder to give
549 reasonable error messages for). These functions have been changed to take
550 arrayrefs in all their forms - so, C<< enum 'My::Type' => [qw(foo bar)] >> is
551 now the preferred way to create an enum type constraint. The old syntax still
552 works for now, but it will hopefully be deprecated and removed in a future
559 L<Moose::Meta::Attribute::Native> has been moved into the Moose core from
560 L<MooseX::AttributeHelpers>. Major changes include:
564 =item C<traits>, not C<metaclass>
566 Method providers are only available via traits.
568 =item C<handles>, not C<provides> or C<curries>
570 The C<provides> syntax was like core Moose C<< handles => HASHREF >>
571 syntax, but with the keys and values reversed. This was confusing,
572 and AttributeHelpers now uses C<< handles => HASHREF >> in a way that
573 should be intuitive to anyone already familiar with how it is used for
576 The C<curries> functionality provided by AttributeHelpers has been
577 generalized to apply to all cases of C<< handles => HASHREF >>, though
578 not every piece of functionality has been ported (currying with a
579 CODEREF is not supported).
581 =item C<empty> is now C<is_empty>, and means empty, not non-empty
583 Previously, the C<empty> method provided by Arrays and Hashes returned true if
584 the attribute was B<not> empty (no elements). Now it returns true if the
585 attribute B<is> empty. It was also renamed to C<is_empty>, to reflect this.
587 =item C<find> was renamed to C<first>, and C<first> and C<last> were removed
589 L<List::Util> refers to the functionality that we used to provide under C<find>
590 as L<first|List::Util/first>, so that will likely be more familiar (and will
591 fit in better if we decide to add more List::Util functions). C<first> and
592 C<last> were removed, since their functionality is easily duplicated with
595 =item Helpers that take a coderef of one argument now use C<$_>
597 Subroutines passed as the first argument to C<first>, C<map>, and C<grep> now
598 receive their argument in C<$_> rather than as a parameter to the subroutine.
599 Helpers that take a coderef of two or more arguments remain using the argument
600 list (there are technical limitations to using C<$a> and C<$b> like C<sort>
603 See L<Moose::Meta::Attribute::Native> for the new documentation.
607 The C<alias> and C<excludes> role parameters have been renamed to C<-alias>
608 and C<-excludes>. The old names still work, but new code should use the new
609 names, and eventually the old ones will be deprecated and removed.
613 C<< use Moose -metaclass => 'Foo' >> now does alias resolution, just like
614 C<-traits> (and the C<metaclass> and C<traits> options to C<has>).
616 Added two functions C<meta_class_alias> and C<meta_attribute_alias> to
617 L<Moose::Util>, to simplify aliasing metaclasses and metatraits. This is
618 a wrapper around the old
620 package Moose::Meta::Class::Custom::Trait::FooTrait;
621 sub register_implementation { 'My::Meta::Trait' }
627 When an attribute generates I<no> accessors, we now warn. This is to help
628 users who forget the C<is> option. If you really do not want any accessors,
629 you can use C<< is => 'bare' >>. You can maintain back compat with older
630 versions of Moose by using something like:
632 ($Moose::VERSION >= 0.84 ? is => 'bare' : ())
634 When an accessor overwrites an existing method, we now warn. To work around
635 this warning (if you really must have this behavior), you can explicitly
636 remove the method before creating it as an accessor:
640 __PACKAGE__->meta->remove_method('foo');
646 When an unknown option is passed to C<has>, we now warn. You can silence
647 the warning by fixing your code. :)
649 The C<Role> type has been deprecated. On its own, it was useless,
650 since it just checked C<< $object->can('does') >>. If you were using
651 it as a parent type, just call C<role_type('Role::Name')> to create an
652 appropriate type instead.
656 C<use Moose::Exporter;> now imports C<strict> and C<warnings> into packages
661 C<DEMOLISHALL> and C<DEMOLISH> now receive an argument indicating whether or
662 not we are in global destruction.
666 Type constraints no longer run coercions for a value that already matches the
667 constraint. This may affect some (arguably buggy) edge case coercions that
668 rely on side effects in the C<via> clause.
672 L<Moose::Exporter> now accepts the C<-metaclass> option for easily
673 overriding the metaclass (without L<metaclass>). This works for classes
678 Added a C<duck_type> sugar function to L<Moose::Util::TypeConstraints>
679 to make integration with non-Moose classes easier. It simply checks if
680 C<< $obj->can() >> a list of methods.
682 A number of methods (mostly inherited from L<Class::MOP>) have been
683 renamed with a leading underscore to indicate their internal-ness. The
684 old method names will still work for a while, but will warn that the
685 method has been renamed. In a few cases, the method will be removed
686 entirely in the future. This may affect MooseX authors who were using
691 Calling C<subtype> with a name as the only argument now throws an
692 exception. If you want an anonymous subtype do:
694 my $subtype = subtype as 'Foo';
696 This is related to the changes in version 0.71_01.
698 The C<is_needed> method in L<Moose::Meta::Method::Destructor> is now
699 only usable as a class method. Previously, it worked as a class or
700 object method, with a different internal implementation for each
703 The internals of making a class immutable changed a lot in Class::MOP
704 0.78_02, and Moose's internals have changed along with it. The
705 external C<< $metaclass->make_immutable >> method still works the same
710 A mutable class accepted C<< Foo->new(undef) >> without complaint,
711 while an immutable class would blow up with an unhelpful error. Now,
712 in both cases we throw a helpful error instead.
714 This "feature" was originally added to allow for cases such as this:
722 return My::Class->new($args);
724 But we decided this is a bad idea and a little too magical, because it
725 can easily mask real errors.
729 Calling C<type> or C<subtype> without the sugar helpers (C<as>,
730 C<where>, C<message>) is now deprecated.
732 As a side effect, this meant we ended up using Perl prototypes on
733 C<as>, and code like this will no longer work:
735 use Moose::Util::TypeConstraints;
736 use Declare::Constraints::Simple -All;
738 subtype 'ArrayOfInts'
740 => IsArrayRef(IsInt);
742 Instead it must be changed to this:
747 where => IsArrayRef(IsInt)
751 If you want to maintain backwards compat with older versions of Moose,
752 you must explicitly test Moose's C<VERSION>:
754 if ( Moose->VERSION < 0.71_01 ) {
755 subtype 'ArrayOfInts'
757 => IsArrayRef(IsInt);
763 where => IsArrayRef(IsInt)
770 We no longer pass the meta-attribute object as a final argument to
771 triggers. This actually changed for inlined code a while back, but the
772 non-inlined version and the docs were still out of date.
774 If by some chance you actually used this feature, the workaround is
775 simple. You fetch the attribute object from out of the C<$self>
776 that is passed as the first argument to trigger, like so:
782 my ( $self, $value ) = @_;
783 my $attr = $self->meta->find_attribute_by_name('foo');
791 If you created a subtype and passed a parent that Moose didn't know
792 about, it simply ignored the parent. Now it automatically creates the
793 parent as a class type. This may not be what you want, but is less
796 You could declare a name with subtype such as "Foo!Bar". Moose would
797 accept this allowed, but if you used it in a parameterized type such
798 as "ArrayRef[Foo!Bar]" it wouldn't work. We now do some vetting on
799 names created via the sugar functions, so that they can only contain
800 alphanumerics, ":", and ".".
804 Methods created via an attribute can now fulfill a C<requires>
805 declaration for a role. Honestly we don't know why Stevan didn't make
806 this work originally, he was just insane or something.
808 Stack traces from inlined code will now report the line and file as
809 being in your class, as opposed to in Moose guts.
813 When a class does not provide all of a role's required methods, the
814 error thrown now mentions all of the missing methods, as opposed to
815 just the first missing method.
817 Moose will no longer inline a constructor for your class unless it
818 inherits its constructor from Moose::Object, and will warn when it
819 doesn't inline. If you want to force inlining anyway, pass
820 C<< replace_constructor => 1 >> to C<make_immutable>.
822 If you want to get rid of the warning, pass C<< inline_constructor =>
827 Removed the (deprecated) C<make_immutable> keyword.
829 Removing an attribute from a class now also removes delegation
830 (C<handles>) methods installed for that attribute. This is correct
831 behavior, but if you were wrongly relying on it you might get bit.
835 Roles now add methods by calling C<add_method>, not
836 C<alias_method>. They make sure to always provide a method object,
837 which will be cloned internally. This means that it is now possible to
838 track the source of a method provided by a role, and even follow its
839 history through intermediate roles. This means that methods added by
840 a role now show up when looking at a class's method list/map.
842 Parameter and Union args are now sorted, this makes Int|Str the same
843 constraint as Str|Int. Also, incoming type constraint strings are
844 normalized to remove all whitespace differences. This is mostly for
845 internals and should not affect outside code.
847 L<Moose::Exporter> will no longer remove a subroutine that the
848 exporting package re-exports. Moose re-exports the Carp::confess
849 function, among others. The reasoning is that we cannot know whether
850 you have also explicitly imported those functions for your own use, so
851 we err on the safe side and always keep them.
855 C<Moose::init_meta> should now be called as a method.
857 New modules for extension writers, L<Moose::Exporter> and
858 L<Moose::Util::MetaRole>.
862 Implemented metaclass traits (and wrote a recipe for it):
864 use Moose -traits => 'Foo'
866 This should make writing small Moose extensions a little
871 Fixed C<coerce> to accept anon types just like C<subtype> can.
874 coerce $some_anon_type => from 'Str' => via { ... };
878 Added C<BUILDARGS>, a new step in C<< Moose::Object->new() >>.
882 Fixed how the C<< is => (ro|rw) >> works with custom defined
883 C<reader>, C<writer> and C<accessor> options. See the below table for
886 is => ro, writer => _foo # turns into (reader => foo, writer => _foo)
887 is => rw, writer => _foo # turns into (reader => foo, writer => _foo)
888 is => rw, accessor => _foo # turns into (accessor => _foo)
889 is => ro, accessor => _foo # error, accesor is rw
893 The C<before/around/after> method modifiers now support regexp
894 matching of method names. NOTE: this only works for classes, it is
895 currently not supported in roles, but, ... patches welcome.
897 The C<has> keyword for roles now accepts the same array ref form that
898 L<Moose>.pm does for classes.
900 A trigger on a read-only attribute is no longer an error, as it's
901 useful to trigger off of the constructor.
903 Subtypes of parameterizable types now are parameterizable types
908 Fixed issue where C<DEMOLISHALL> was eating the value in C<$@>, and so
909 not working correctly. It still kind of eats them, but so does vanilla
914 Inherited attributes may now be extended without restriction on the
915 type ('isa', 'does').
917 The entire set of Moose::Meta::TypeConstraint::* classes were
918 refactored in this release. If you were relying on their internals you
919 should test your code carefully.
923 Documenting the use of '+name' with attributes that come from recently
924 composed roles. It makes sense, people are using it, and so why not
925 just officially support it.
927 The C<< Moose::Meta::Class->create >> method now supports roles.
929 It is now possible to make anonymous enum types by passing C<enum> an
930 array reference instead of the C<< enum $name => @values >>.
934 Added the C<make_immutable> keyword as a shortcut to calling
935 C<make_immutable> on the meta object. This eventually got removed!
937 Made C<< init_arg => undef >> work in Moose. This means "do not accept
938 a constructor parameter for this attribute".
940 Type errors now use the provided message. Prior to this release they
945 Moose is now a postmodern object system :)
947 The Role system was completely refactored. It is 100% backwards
948 compat, but the internals were totally changed. If you relied on the
949 internals then you are advised to test carefully.
951 Added method exclusion and aliasing for Roles in this release.
953 Added the L<Moose::Util::TypeConstraints::OptimizedConstraints>
956 Passing a list of values to an accessor (which is only expecting one
957 value) used to be silently ignored, now it throws an error.
961 Added parameterized types and did a pretty heavy refactoring of the
962 type constraint system.
964 Better framework extensibility and better support for "making your own
967 =head1 0.25 or before
969 Honestly, you shouldn't be using versions of Moose that are this old,
970 so many bug fixes and speed improvements have been made you would be
971 crazy to not upgrade.
973 Also, I am tired of going through the Changelog so I am stopping here,
974 if anyone would like to continue this please feel free.