Revert the change that unimported strict & warnings on no Moose(::Role,::Exporter)

[gitmo/Moose.git] / lib / Moose / Manual / Delta.pod

diff --git a/lib/Moose/Manual/Delta.pod b/lib/Moose/Manual/Delta.pod
index 28a7417..93fd31b 100644 (file)
--- a/lib/Moose/Manual/Delta.pod
+++ b/lib/Moose/Manual/Delta.pod
@@ -16,6 +16,16 @@ feature.  If you encounter a problem and have a solution but don't see
 it documented here, or think we missed an important feature, please
 send us a patch.
 
+=head1 1.09
+
+=item C<no Moose>, C<no Moose::Role>, and C<no Moose::Exporter> no longer unimport strict and warnings
+
+This change was made in 1.05, and has now been reverted. We don't know if the
+user has explicitly loaded strict or warnings outside on their own, and
+unimporting them is just broken in that case.
+
+=head1 1.05
+
 =over 4
 
 =item L<Moose::Object/BUILD> methods are now called when calling C<new_object>
@@ -32,6 +42,16 @@ In the interest of having C<no Moose> clean up everything that C<use Moose>
 does in the calling scope, C<no Moose> (as well as all other
 L<Moose::Exporter>-using modules) now unimports strict and warnings.
 
+=item Metaclass compatibility checking and fixing should be much more robust
+
+The L<metaclass compatibility|Moose/METACLASS COMPATIBILITY AND MOOSE> checking
+and fixing algorithms have been completely rewritten, in both Class::MOP and
+Moose. This should resolve many confusing errors when dealing with non-Moose
+inheritance and with custom metaclasses for things like attributes,
+constructors, etc. For correct code, the only thing that should require a
+change is that custom error metaclasses must now inherit from
+L<Moose::Error::Default>.
+
 =back
 
 =head1 1.02