Prep for removing deprecated features or making them throw an error.
[gitmo/Moose.git] / lib / Moose / Manual / Delta.pod
CommitLineData
daa0fd7d 1package Moose::Manual::Delta;
2
3# ABSTRACT: Important Changes in Moose
600f7f85 4
daa0fd7d 5__END__
600f7f85 6
daa0fd7d 7=pod
600f7f85 8
9=head1 DESCRIPTION
10
0f13f53c 11This documents any important or noteworthy changes in Moose, with a
12focus on backwards. This does duplicate data from the F<Changes> file,
13but aims to provide more details and when possible workarounds.
14
15Besides helping keep up with changes, you can also use this document
16for finding the lowest version of Moose that supported a given
17feature. If you encounter a problem and have a solution but don't see
18it documented here, or think we missed an important feature, please
19send us a patch.
600f7f85 20
13eb2af6 21=head1 NEXT
22
23=over 4
24
25=item Roles have their own default attribute metaclass
26
27Previously, when a role was applied to a class, it would use the attribute
28metaclass defined in the class when copying over the attributes in the role.
29This was wrong, because for instance, using L<MooseX::FollowPBP> in the class
30would end up renaming all of the accessors generated by the role, some of which
31may be being called in the role, causing it to break. Roles now keep track of
32their own attribute metaclass to use by default when being applied to a class
33(defaulting to Moose::Meta::Attribute). This is modifiable using
34L<Moose::Util::MetaRole> by passing the C<applied_attribute> key to the
35C<role_metaroles> option, as in:
36
37 Moose::Util::MetaRole::apply_metaroles(
38 for => __PACKAGE__,
39 class_metaroles => {
40 attribute => ['My::Meta::Role::Attribute'],
41 },
42 role_metaroles => {
43 applied_attribute => ['My::Meta::Role::Attribute'],
44 },
45 );
46
14bda293 47=item Most deprecated APIs/features are slated for removal in Moose 2.0200
48
49Most of the deprecated APIs and features in Moose will start throwing an error
50in Moose 2.0200. Some of the features will go away entirely, and some will
51simply throw an error.
52
53The things on the chopping block are:
54
55=over 8
56
57=item * Old public methods in Class::MOP and Moose
58
59This includes things like C<< Class::MOP::Class->get_attribute_map >>, C<<
60Class::MOP::Class->construct_instance >>, and many others. These were
61deprecated in L<Class::MOP> 0.80_01, release on April 5, 2009.
62
63These methods will be removed entirely in Moose 2.0200.
64
65=item * Old public functions in Class::MOP
66
67This include C<Class::MOP::subname>, C<Class::MOP::in_global_destruction>, and
68the C<Class::MOP::HAS_ISAREV> constant. The first two were deprecated in 0.84,
69and the last in 0.80. Class::MOP 0.84 was released on May 12, 2009.
70
71These functions will be removed entirely in Moose 2.0200.
72
73=item * The C<alias> and C<excludes> option for role composition
74
75These were renamed to C<-alias> and C<-excludes> in Moose 0.89, released on
76August 13, 2009.
77
78Passing these will throw an error in Moose 2.0200.
79
80=item * The old L<Moose::Util::MetaRole> API
81
82This include the C<apply_metaclass_roles()> function, as well as passing the
83C<for_class> or any key ending in C<_roles> to C<apply_metaroles()>. This was
84deprecated in Moose 0.93_01, released on January 4, 2010.
85
86These will all throw an error in Moose 2.0200.
87
88=item * Passing plain lists to C<type()> or C<subtype()>
89
90The old API for these functions allowed you to pass a plain list of parameter,
91rather than a list of hash references (which is what C<as()>, C<where>,
92etc. return). This was deprecated in Moose 0.71_01, released on February 22,
932009.
94
95This will throw an error in Moose 2.0200.
96
97=item * The Role subtype
98
99This subtype was deprecated in Moose 0.84, released on June 26, 2009.
100
101This will be removed entirely in Moose 2.0200.
102
103=back
104
13eb2af6 105=back
106
9796131f 107=head1 1.16
108
109=over 4
110
111=item Configurable stacktraces
112
113Classes which use the L<Moose::Error::Default> error class can now have
114stacktraces disabled by setting the C<MOOSE_ERROR_STYLE> env var to C<croak>.
115This is experimental, fairly incomplete, and won't work in all cases (because
116Moose's error system in general is all of these things), but this should allow
117for reducing at least some of the verbosity in most cases.
118
119=back
120
adff0aa1 121=head1 1.15
d6ce97b9 122
123=over 4
124
adff0aa1 125=item Native Delegations
d6ce97b9 126
127In previous versions of Moose, the Native delegations were created as
128closures. The generated code was often quite slow compared to doing the same
129thing by hand. For example, the Array's push delegation ended up doing
130something like this:
131
132 push @{ $self->$reader() }, @_;
133
134If the attribute was created without a reader, the C<$reader> sub reference
135followed a very slow code path. Even with a reader, this is still slower than
136it needs to be.
137
138Native delegations are now generated as inline code, just like other
139accessors, so we can access the slot directly.
140
141In addition, native traits now do proper constraint checking in all cases. In
142particular, constraint checking has been improved for array and hash
143references. Previously, only the I<contained> type (the C<Str> in
144C<HashRef[Str]>) would be checked when a new value was added to the
145collection. However, if there was a constraint that applied to the whole
146value, this was never checked.
147
148In addition, coercions are now called on the whole value.
149
27719606 150The delegation methods now do more argument checking. All of the methods check
151that a valid number of arguments were passed to the method. In addition, the
152delegation methods check that the arguments are sane (array indexes, hash
153keys, numbers, etc.) when applicable. We have tried to emulate the behavior of
154Perl builtins as much as possible.
155
d6ce97b9 156Finally, triggers are called whenever the value of the attribute is changed by
157a Native delegation.
158
c99ddeb7 159These changes are only likely to break code in a few cases.
160
ca8d6244 161The inlining code may or may not preserve the original reference when changes
c99ddeb7 162are made. In some cases, methods which change the value may replace it
163entirely. This will break tied values.
164
165If you have a typed arrayref or hashref attribute where the type enforces a
166constraint on the whole collection, this constraint will now be checked. It's
167possible that code which previously ran without errors will now cause the
168constraint to fail. However, presumably this is a good thing ;)
d6ce97b9 169
27719606 170If you are passing invalid arguments to a delegation which were previously
ca8d6244 171being ignored, these calls will now fail.
27719606 172
c99ddeb7 173If your code relied on the trigger only being called for a regular writer,
174that may cause problems.
d6ce97b9 175
176As always, you are encouraged to test before deploying the latest version of
177Moose to production.
178
c787d26e 179=item Defaults is and default for String, Counter, and Bool
180
d21ebae8 181A few native traits (String, Counter, Bool) provide default values of "is" and
c787d26e 182"default" when you created an attribute. Allowing them to provide these values
183is now deprecated. Supply the value yourself when creating the attribute.
184
a2084f68 185=item The C<meta> method
186
187Moose and Class::MOP have been cleaned up internally enough to make the
188C<meta> method that you get by default optional. C<use Moose> and
189C<use Moose::Role> now can take an additional C<-meta_name> option, which
190tells Moose what name to use when installing the C<meta> method. Passing
191C<undef> to this option suppresses generation of the C<meta> method
192entirely. This should be useful for users of modules which also use a C<meta>
193method or function, such as L<Curses> or L<Rose::DB::Object>.
194
d6ce97b9 195=back
196
aee0741b 197=head1 1.09
198
7dacb294 199=over 4
200
4c7d1018 201=item All deprecated features now warn
202
203Previously, deprecation mostly consisted of simply saying "X is deprecated" in
204the Changes file. We were not very consistent about actually warning. Now, all
205deprecated features still present in Moose actually give a warning. The
206warning is issued once per calling package. See L<Moose::Deprecated> for more
207details.
208
2b54d2a6 209=item You cannot pass C<< coerce => 1 >> unless the attribute's type constraint has a coercion
210
211Previously, this was accepted, and it sort of worked, except that if you
212attempted to set the attribute after the object was created, you would get a
213runtime error.
214
aa6da652 215Now you will get a warning when you attempt to define the attribute.
2b54d2a6 216
aee0741b 217=item C<no Moose>, C<no Moose::Role>, and C<no Moose::Exporter> no longer unimport strict and warnings
218
219This change was made in 1.05, and has now been reverted. We don't know if the
dee8c866 220user has explicitly loaded strict or warnings on their own, and unimporting
221them is just broken in that case.
aee0741b 222
59caebc4 223=item Reversed logic when defining which options can be changed
7782e1da 224
da7efd4c 225L<Moose::Meta::Attribute> now allows all options to be changed in an
226overridden attribute. The previous behaviour required each option to be
227whitelisted using the C<legal_options_for_inheritance> method. This method has
228been removed, and there is a new method, C<illegal_options_for_inheritance>,
229which can now be used to prevent certain options from being changeable.
7782e1da 230
da7efd4c 231In addition, we only throw an error if the illegal option is actually
232changed. If the superclass didn't specify this option at all when defining the
233attribute, the subclass version can still add it as an option.
dede9732 234
235Example of overriding this in an attribute trait:
7782e1da 236
dede9732 237 package Bar::Meta::Attribute;
238 use Moose::Role;
7782e1da 239
240 has 'my_illegal_option' => (
da7efd4c 241 isa => 'CodeRef',
242 is => 'rw',
7782e1da 243 );
244
245 around illegal_options_for_inheritance => sub {
da7efd4c 246 return ( shift->(@_), qw/my_illegal_option/ );
7782e1da 247 };
248
7dacb294 249=back
250
e462f6f3 251=head1 1.05
252
a19ae3d7 253=over 4
254
255=item L<Moose::Object/BUILD> methods are now called when calling C<new_object>
256
257Previously, C<BUILD> methods would only be called from C<Moose::Object::new>,
258but now they are also called when constructing an object via
259C<Moose::Meta::Class::new_object>. C<BUILD> methods are an inherent part of the
260object construction process, and this should make C<< $meta->new_object >>
261actually usable without forcing people to use C<< $meta->name->new >>.
262
2fee26f1 263=item C<no Moose>, C<no Moose::Role>, and C<no Moose::Exporter> now unimport strict and warnings
264
265In the interest of having C<no Moose> clean up everything that C<use Moose>
266does in the calling scope, C<no Moose> (as well as all other
267L<Moose::Exporter>-using modules) now unimports strict and warnings.
268
f46a74bf 269=item Metaclass compatibility checking and fixing should be much more robust
270
271The L<metaclass compatibility|Moose/METACLASS COMPATIBILITY AND MOOSE> checking
272and fixing algorithms have been completely rewritten, in both Class::MOP and
273Moose. This should resolve many confusing errors when dealing with non-Moose
274inheritance and with custom metaclasses for things like attributes,
918b5cef 275constructors, etc. For correct code, the only thing that should require a
276change is that custom error metaclasses must now inherit from
277L<Moose::Error::Default>.
f46a74bf 278
a19ae3d7 279=back
280
8ff79890 281=head1 1.02
282
283=over 4
284
285=item Moose::Meta::TypeConstraint::Class is_subtype_of behavior
286
287Earlier versions of L<is_subtype_of|Moose::Meta::TypeConstraint::Class/is_subtype_of>
288would incorrectly return true when called with itself, its own TC name or
289its class name as an argument. (i.e. $foo_tc->is_subtype_of('Foo') == 1) This
290behavior was a caused by C<isa> being checked before the class name. The old
291behavior can be accessed with L<is_type_of|Moose::Meta::TypeConstraint::Class/is_type_of>
292
293=back
294
12885414 295=head1 1.00
296
297=over 4
298
299=item Moose::Meta::Attribute::Native::Trait::Code no longer creates reader methods by default
300
301Earlier versions of L<Moose::Meta::Attribute::Native::Trait::Code> created
302read-only accessors for the attributes it's been applied to, even if you didn't
303ask for it with C<< is => 'ro' >>. This incorrect behaviour has now been fixed.
304
305=back
306
775666aa 307=head1 0.95
308
309=over 4
310
311=item Moose::Util add_method_modifier behavior
312
313add_method_modifier (and subsequently the sugar functions Moose::before,
314Moose::after, and Moose::around) can now accept arrayrefs, with the same
315behavior as lists. Types other than arrayref and regexp result in an error.
316
317=back
318
5b7b27e2 319=head1 0.93_01 and 0.94
320
321=over 4
322
f785aad8 323=item Moose::Util::MetaRole API has changed
324
325The C<apply_metaclass_roles> function is now called C<apply_metaroles>. The
326way arguments are supplied has been changed to force you to distinguish
327between metaroles applied to L<Moose::Meta::Class> (and helpers) versus
328L<Moose::Meta::Role>.
329
330The old API still works, but will warn in a future release, and eventually be
331removed.
332
333=item Moose::Meta::Role has real attributes
334
335The attributes returned by L<Moose::Meta::Role> are now instances of the
336L<Moose::Meta::Role::Attribute> class, instead of bare hash references.
337
5b7b27e2 338=item "no Moose" now removes C<blessed> and C<confess>
339
340Moose is now smart enough to know exactly what it exported, even when it
341re-exports functions from other packages. When you unimport Moose, it will
342remove these functions from your namespace unless you I<also> imported them
343directly from their respective packages.
344
345If you have a C<no Moose> in your code I<before> you call C<blessed> or
346C<confess>, your code will break. You can either move the C<no Moose> call
347later in your code, or explicitly import the relevant functions from the
348packages that provide them.
349
350=item L<Moose::Exporter> is smarter about unimporting re-exports
351
352The change above comes from a general improvement to L<Moose::Exporter>. It
353will now unimport any function it exports, even if that function is a
354re-export from another package.
355
f427b505 356=item Attributes in roles can no longer override class attributes with "+foo"
357
358Previously, this worked more or less accidentally, because role attributes
359weren't objects. This was never documented, but a few MooseX modules took
360advantage of this.
361
362=item The composition_class_roles attribute in L<Moose::Meta::Role> is now a method
363
364This was done to make it possible for roles to alter the the list of
365composition class roles by applying a method modifiers. Previously, this was
366an attribute and MooseX modules override it. Since that no longer works, this
367was made a method.
368
369This I<should> be an attribute, so this may switch back to being an attribute
370in the future if we can figure out how to make this work.
371
5b7b27e2 372=back
373
c378a61a 374=head1 0.93
375
376=over 4
377
378=item Calling $object->new() is no longer deprecated
379
76c89056 380We decided to undeprecate this. Now it just works.
c378a61a 381
d99ec58b 382=item Both C<get_method_map> and C<get_attribute_map> is deprecated
fa6da135 383
d99ec58b 384These metaclass methods were never meant to be public, and they are both now
385deprecated. The work around if you still need the functionality they provided
386is to iterate over the list of names manually.
fa6da135 387
388 my %fields = map { $_ => $meta->get_attribute($_) } $meta->get_attribute_list;
389
d99ec58b 390This was actually a change in L<Class::MOP>, but this version of Moose
391requires a version of L<Class::MOP> that includes said change.
392
c378a61a 393=back
394
b98ef150 395=head1 0.90
871f82f8 396
c985327a 397=over 4
398
93ef4ba1 399=item Added Native delegation for Code refs
400
401See L<Moose::Meta::Attribute::Native::Trait::Code> for details.
402
3f5ff7d0 403=item Calling $object->new() is deprecated
404
405Moose has long supported this, but it's never really been documented, and we
406don't think this is a good practice. If you want to construct an object from
407an existing object, you should provide some sort of alternate constructor like
408C<< $object->clone >>.
409
410Calling C<< $object->new >> now issues a warning, and will be an error in a
411future release.
412
19e60fdd 413=item Moose no longer warns if you call C<make_immutable> for a class with mutable ancestors
414
415While in theory this is a good thing to warn about, we found so many
416exceptions to this that doing this properly became quite problematic.
417
93ef4ba1 418=back
419
def57e8d 420=head1 0.89_02
93ef4ba1 421
422=over 4
4f0d4488 423
871f82f8 424=item New Native delegation methods from L<List::Util> and L<List::MoreUtils>
425
426In particular, we now have C<reduce>, C<shuffle>, C<uniq>, and C<natatime>.
427
3023f1e4 428=item The Moose::Exporter with_caller feature is now deprecated
429
430Use C<with_meta> instead. The C<with_caller> option will start warning in a
431future release.
432
9b9a5a07 433=item Moose now warns if you call C<make_immutable> for a class with mutable ancestors
434
435This is dangerous because modifying a class after a subclass has been
90b20bd6 436immutabilized will lead to incorrect results in the subclass, due to inlining,
9b9a5a07 437caching, etc. This occasionally happens accidentally, when a class loads one
438of its subclasses in the middle of its class definition, so pointing out that
439this may cause issues should be helpful. Metaclasses (classes that inherit
440from L<Class::MOP::Object>) are currently exempt from this check, since at the
90b20bd6 441moment we aren't very consistent about which metaclasses we immutabilize.
9b9a5a07 442
bce5d4a5 443=item C<enum> and C<duck_type> now take arrayrefs for all forms
444
445Previously, calling these functions with a list would take the first element of
446the list as the type constraint name, and use the remainder as the enum values
447or method names. This makes the interface inconsistent with the anon-type forms
448of these functions (which must take an arrayref), and a free-form list where
449the first value is sometimes special is hard to validate (and harder to give
450reasonable error messages for). These functions have been changed to take
451arrayrefs in all their forms - so, C<< enum 'My::Type' => [qw(foo bar)] >> is
452now the preferred way to create an enum type constraint. The old syntax still
453works for now, but it will hopefully be deprecated and removed in a future
454release.
455
871f82f8 456=back
457
def57e8d 458=head1 0.89_01
a3d98218 459
af44c00c 460L<Moose::Meta::Attribute::Native> has been moved into the Moose core from
a3d98218 461L<MooseX::AttributeHelpers>. Major changes include:
462
ebaaa391 463=over 4
a3d98218 464
465=item C<traits>, not C<metaclass>
466
93ced2bd 467Method providers are only available via traits.
a3d98218 468
469=item C<handles>, not C<provides> or C<curries>
470
93ced2bd 471The C<provides> syntax was like core Moose C<< handles => HASHREF >>
472syntax, but with the keys and values reversed. This was confusing,
473and AttributeHelpers now uses C<< handles => HASHREF >> in a way that
474should be intuitive to anyone already familiar with how it is used for
475other attributes.
a3d98218 476
93ced2bd 477The C<curries> functionality provided by AttributeHelpers has been
478generalized to apply to all cases of C<< handles => HASHREF >>, though
479not every piece of functionality has been ported (currying with a
480CODEREF is not supported).
a3d98218 481
1853a27e 482=item C<empty> is now C<is_empty>, and means empty, not non-empty
af44c00c 483
484Previously, the C<empty> method provided by Arrays and Hashes returned true if
485the attribute was B<not> empty (no elements). Now it returns true if the
1853a27e 486attribute B<is> empty. It was also renamed to C<is_empty>, to reflect this.
af44c00c 487
9a14bd29 488=item C<find> was renamed to C<first>, and C<first> and C<last> were removed
28b96142 489
490L<List::Util> refers to the functionality that we used to provide under C<find>
491as L<first|List::Util/first>, so that will likely be more familiar (and will
9a14bd29 492fit in better if we decide to add more List::Util functions). C<first> and
493C<last> were removed, since their functionality is easily duplicated with
494curries of C<get>.
28b96142 495
496=item Helpers that take a coderef of one argument now use C<$_>
497
498Subroutines passed as the first argument to C<first>, C<map>, and C<grep> now
499receive their argument in C<$_> rather than as a parameter to the subroutine.
500Helpers that take a coderef of two or more arguments remain using the argument
501list (there are technical limitations to using C<$a> and C<$b> like C<sort>
502does).
503
af44c00c 504See L<Moose::Meta::Attribute::Native> for the new documentation.
a3d98218 505
ebaaa391 506=back
507
85e2b15a 508The C<alias> and C<excludes> role parameters have been renamed to C<-alias>
509and C<-excludes>. The old names still work, but new code should use the new
510names, and eventually the old ones will be deprecated and removed.
511
def57e8d 512=head1 0.89
4ada9618 513
8a8856de 514C<< use Moose -metaclass => 'Foo' >> now does alias resolution, just like
515C<-traits> (and the C<metaclass> and C<traits> options to C<has>).
516
27f2f43f 517Added two functions C<meta_class_alias> and C<meta_attribute_alias> to
518L<Moose::Util>, to simplify aliasing metaclasses and metatraits. This is
519a wrapper around the old
520
521 package Moose::Meta::Class::Custom::Trait::FooTrait;
522 sub register_implementation { 'My::Meta::Trait' }
523
524way of doing this.
525
def57e8d 526=head1 0.84
4831e2de 527
9f52cce5 528When an attribute generates I<no> accessors, we now warn. This is to help
529users who forget the C<is> option. If you really do not want any accessors,
3de02fd8 530you can use C<< is => 'bare' >>. You can maintain back compat with older
531versions of Moose by using something like:
532
533 ($Moose::VERSION >= 0.84 ? is => 'bare' : ())
9f52cce5 534
535When an accessor overwrites an existing method, we now warn. To work around
536this warning (if you really must have this behavior), you can explicitly
537remove the method before creating it as an accessor:
538
539 sub foo {}
540
541 __PACKAGE__->meta->remove_method('foo');
542
543 has foo => (
544 is => 'ro',
545 );
546
547When an unknown option is passed to C<has>, we now warn. You can silence
548the warning by fixing your code. :)
549
4831e2de 550The C<Role> type has been deprecated. On its own, it was useless,
551since it just checked C<< $object->can('does') >>. If you were using
552it as a parent type, just call C<role_type('Role::Name')> to create an
553appropriate type instead.
554
def57e8d 555=head1 0.78
7d6b451f 556
557C<use Moose::Exporter;> now imports C<strict> and C<warnings> into packages
558that use it.
559
def57e8d 560=head1 0.77
c3fdacda 561
562C<DEMOLISHALL> and C<DEMOLISH> now receive an argument indicating whether or
563not we are in global destruction.
564
def57e8d 565=head1 0.76
00c61603 566
9f0b3b64 567Type constraints no longer run coercions for a value that already matches the
568constraint. This may affect some (arguably buggy) edge case coercions that
569rely on side effects in the C<via> clause.
570
def57e8d 571=head1 0.75
f869fc4a 572
573L<Moose::Exporter> now accepts the C<-metaclass> option for easily
574overriding the metaclass (without L<metaclass>). This works for classes
575and roles.
576
def57e8d 577=head1 0.74
39ab7714 578
85cf0647 579Added a C<duck_type> sugar function to L<Moose::Util::TypeConstraints>
580to make integration with non-Moose classes easier. It simply checks if
581C<< $obj->can() >> a list of methods.
39ab7714 582
612fd754 583A number of methods (mostly inherited from L<Class::MOP>) have been
584renamed with a leading underscore to indicate their internal-ness. The
585old method names will still work for a while, but will warn that the
586method has been renamed. In a few cases, the method will be removed
587entirely in the future. This may affect MooseX authors who were using
588these methods.
589
def57e8d 590=head1 0.73
600f7f85 591
0f13f53c 592Calling C<subtype> with a name as the only argument now throws an
600f7f85 593exception. If you want an anonymous subtype do:
594
595 my $subtype = subtype as 'Foo';
596
0f13f53c 597This is related to the changes in version 0.71_01.
600f7f85 598
501db4e6 599The C<is_needed> method in L<Moose::Meta::Method::Destructor> is now
600only usable as a class method. Previously, it worked as a class or
601object method, with a different internal implementation for each
602version.
603
604The internals of making a class immutable changed a lot in Class::MOP
6050.78_02, and Moose's internals have changed along with it. The
606external C<< $metaclass->make_immutable >> method still works the same
607way.
608
def57e8d 609=head1 0.72
600f7f85 610
0f13f53c 611A mutable class accepted C<< Foo->new(undef) >> without complaint,
612while an immutable class would blow up with an unhelpful error. Now,
613in both cases we throw a helpful error instead.
600f7f85 614
0f13f53c 615This "feature" was originally added to allow for cases such as this:
600f7f85 616
617 my $args;
0f13f53c 618
619 if ( something() ) {
620 $args = {...};
600f7f85 621 }
0f13f53c 622
600f7f85 623 return My::Class->new($args);
624
0f13f53c 625But we decided this is a bad idea and a little too magical, because it
626can easily mask real errors.
600f7f85 627
def57e8d 628=head1 0.71_01
600f7f85 629
0f13f53c 630Calling C<type> or C<subtype> without the sugar helpers (C<as>,
631C<where>, C<message>) is now deprecated.
632
633As a side effect, this meant we ended up using Perl prototypes on
634C<as>, and code like this will no longer work:
600f7f85 635
636 use Moose::Util::TypeConstraints;
637 use Declare::Constraints::Simple -All;
0f13f53c 638
639 subtype 'ArrayOfInts'
600f7f85 640 => as 'ArrayRef'
641 => IsArrayRef(IsInt);
642
643Instead it must be changed to this:
644
0f13f53c 645 subtype(
646 'ArrayOfInts' => {
647 as => 'ArrayRef',
648 where => IsArrayRef(IsInt)
649 }
600f7f85 650 );
651
0f13f53c 652If you want to maintain backwards compat with older versions of Moose,
653you must explicitly test Moose's C<VERSION>:
600f7f85 654
0f13f53c 655 if ( Moose->VERSION < 0.71_01 ) {
656 subtype 'ArrayOfInts'
600f7f85 657 => as 'ArrayRef'
658 => IsArrayRef(IsInt);
659 }
660 else {
0f13f53c 661 subtype(
662 'ArrayOfInts' => {
663 as => 'ArrayRef',
664 where => IsArrayRef(IsInt)
665 }
600f7f85 666 );
667 }
668
def57e8d 669=head1 0.70
600f7f85 670
0f13f53c 671We no longer pass the meta-attribute object as a final argument to
672triggers. This actually changed for inlined code a while back, but the
673non-inlined version and the docs were still out of date.
674
675If by some chance you actually used this feature, the workaround is
676simple. You fetch the attribute object from out of the C<$self>
677that is passed as the first argument to trigger, like so:
678
679 has 'foo' => (
680 is => 'ro',
681 isa => 'Any',
682 trigger => sub {
683 my ( $self, $value ) = @_;
684 my $attr = $self->meta->find_attribute_by_name('foo');
685
686 # ...
687 }
688 );
600f7f85 689
def57e8d 690=head1 0.66
600f7f85 691
0f13f53c 692If you created a subtype and passed a parent that Moose didn't know
693about, it simply ignored the parent. Now it automatically creates the
694parent as a class type. This may not be what you want, but is less
695broken than before.
600f7f85 696
0f13f53c 697You could declare a name with subtype such as "Foo!Bar". Moose would
698accept this allowed, but if you used it in a parameterized type such
699as "ArrayRef[Foo!Bar]" it wouldn't work. We now do some vetting on
700names created via the sugar functions, so that they can only contain
701alphanumerics, ":", and ".".
600f7f85 702
def57e8d 703=head1 0.65
600f7f85 704
705Methods created via an attribute can now fulfill a C<requires>
0f13f53c 706declaration for a role. Honestly we don't know why Stevan didn't make
707this work originally, he was just insane or something.
600f7f85 708
0f13f53c 709Stack traces from inlined code will now report the line and file as
710being in your class, as opposed to in Moose guts.
600f7f85 711
def57e8d 712=head1 0.62_02
600f7f85 713
0f13f53c 714When a class does not provide all of a role's required methods, the
715error thrown now mentions all of the missing methods, as opposed to
716just the first missing method.
600f7f85 717
0f13f53c 718Moose will no longer inline a constructor for your class unless it
5e26e3f2 719inherits its constructor from Moose::Object, and will warn when it
720doesn't inline. If you want to force inlining anyway, pass
b84f64da 721C<< replace_constructor => 1 >> to C<make_immutable>.
0f13f53c 722
723If you want to get rid of the warning, pass C<< inline_constructor =>
fbf7ba85 7240 >>.
600f7f85 725
def57e8d 726=head1 0.62
600f7f85 727
0f13f53c 728Removed the (deprecated) C<make_immutable> keyword.
600f7f85 729
730Removing an attribute from a class now also removes delegation
0f13f53c 731(C<handles>) methods installed for that attribute. This is correct
600f7f85 732behavior, but if you were wrongly relying on it you might get bit.
733
def57e8d 734=head1 0.58
600f7f85 735
0f13f53c 736Roles now add methods by calling C<add_method>, not
737C<alias_method>. They make sure to always provide a method object,
738which will be cloned internally. This means that it is now possible to
739track the source of a method provided by a role, and even follow its
740history through intermediate roles. This means that methods added by
741a role now show up when looking at a class's method list/map.
742
743Parameter and Union args are now sorted, this makes Int|Str the same
744constraint as Str|Int. Also, incoming type constraint strings are
745normalized to remove all whitespace differences. This is mostly for
746internals and should not affect outside code.
747
748L<Moose::Exporter> will no longer remove a subroutine that the
749exporting package re-exports. Moose re-exports the Carp::confess
750function, among others. The reasoning is that we cannot know whether
751you have also explicitly imported those functions for your own use, so
752we err on the safe side and always keep them.
600f7f85 753
def57e8d 754=head1 0.56
600f7f85 755
0f13f53c 756C<Moose::init_meta> should now be called as a method.
600f7f85 757
0f13f53c 758New modules for extension writers, L<Moose::Exporter> and
759L<Moose::Util::MetaRole>.
600f7f85 760
def57e8d 761=head1 0.55_01
600f7f85 762
763Implemented metaclass traits (and wrote a recipe for it):
764
765 use Moose -traits => 'Foo'
766
767This should make writing small Moose extensions a little
768easier.
769
def57e8d 770=head1 0.55
600f7f85 771
772Fixed C<coerce> to accept anon types just like C<subtype> can.
773So that you can do:
774
775 coerce $some_anon_type => from 'Str' => via { ... };
776
def57e8d 777=head1 0.51
600f7f85 778
52da380a 779Added C<BUILDARGS>, a new step in C<< Moose::Object->new() >>.
600f7f85 780
def57e8d 781=head1 0.49
600f7f85 782
0f13f53c 783Fixed how the C<< is => (ro|rw) >> works with custom defined
784C<reader>, C<writer> and C<accessor> options. See the below table for
600f7f85 785details:
786
787 is => ro, writer => _foo # turns into (reader => foo, writer => _foo)
788 is => rw, writer => _foo # turns into (reader => foo, writer => _foo)
789 is => rw, accessor => _foo # turns into (accessor => _foo)
790 is => ro, accessor => _foo # error, accesor is rw
791
def57e8d 792=head1 0.45
600f7f85 793
0f13f53c 794The C<before/around/after> method modifiers now support regexp
795matching of method names. NOTE: this only works for classes, it is
796currently not supported in roles, but, ... patches welcome.
600f7f85 797
0f13f53c 798The C<has> keyword for roles now accepts the same array ref form that
799L<Moose>.pm does for classes.
600f7f85 800
0f13f53c 801A trigger on a read-only attribute is no longer an error, as it's
802useful to trigger off of the constructor.
600f7f85 803
0f13f53c 804Subtypes of parameterizable types now are parameterizable types
805themselves.
600f7f85 806
def57e8d 807=head1 0.44
600f7f85 808
0f13f53c 809Fixed issue where C<DEMOLISHALL> was eating the value in C<$@>, and so
810not working correctly. It still kind of eats them, but so does vanilla
811perl.
600f7f85 812
def57e8d 813=head1 0.41
600f7f85 814
0f13f53c 815Inherited attributes may now be extended without restriction on the
600f7f85 816type ('isa', 'does').
817
0f13f53c 818The entire set of Moose::Meta::TypeConstraint::* classes were
819refactored in this release. If you were relying on their internals you
820should test your code carefully.
600f7f85 821
def57e8d 822=head1 0.40
600f7f85 823
0f13f53c 824Documenting the use of '+name' with attributes that come from recently
825composed roles. It makes sense, people are using it, and so why not
826just officially support it.
600f7f85 827
0f13f53c 828The C<< Moose::Meta::Class->create >> method now supports roles.
600f7f85 829
86b96832 830It is now possible to make anonymous enum types by passing C<enum> an
831array reference instead of the C<< enum $name => @values >>.
600f7f85 832
def57e8d 833=head1 0.37
600f7f85 834
0f13f53c 835Added the C<make_immutable> keyword as a shortcut to calling
836C<make_immutable> on the meta object. This eventually got removed!
600f7f85 837
0f13f53c 838Made C<< init_arg => undef >> work in Moose. This means "do not accept
600f7f85 839a constructor parameter for this attribute".
840
0f13f53c 841Type errors now use the provided message. Prior to this release they
842didn't.
600f7f85 843
def57e8d 844=head1 0.34
600f7f85 845
846Moose is now a postmodern object system :)
847
0f13f53c 848The Role system was completely refactored. It is 100% backwards
849compat, but the internals were totally changed. If you relied on the
850internals then you are advised to test carefully.
600f7f85 851
852Added method exclusion and aliasing for Roles in this release.
853
0f13f53c 854Added the L<Moose::Util::TypeConstraints::OptimizedConstraints>
855module.
600f7f85 856
0f13f53c 857Passing a list of values to an accessor (which is only expecting one
858value) used to be silently ignored, now it throws an error.
600f7f85 859
def57e8d 860=head1 0.26
600f7f85 861
0f13f53c 862Added parameterized types and did a pretty heavy refactoring of the
863type constraint system.
600f7f85 864
7bb4be82 865Better framework extensibility and better support for "making your own
0f13f53c 866Moose".
600f7f85 867
def57e8d 868=head1 0.25 or before
600f7f85 869
0f13f53c 870Honestly, you shouldn't be using versions of Moose that are this old,
871so many bug fixes and speed improvements have been made you would be
872crazy to not upgrade.
600f7f85 873
0f13f53c 874Also, I am tired of going through the Changelog so I am stopping here,
875if anyone would like to continue this please feel free.
600f7f85 876
0f13f53c 877=cut