From: Shawn M Moore <sartak@gmail.com>
Date: Sat, 25 Apr 2009 13:36:12 +0000 (-0400)
Subject: Doc the reversion of THE WARNING
X-Git-Tag: 0.76~6
X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=c4a107bf466a40b87942c7b7cd9c0c56bbf4b531;p=gitmo%2FMoose.git

Doc the reversion of THE WARNING
---

diff --git a/Changes b/Changes
index 83db4f5..f495553 100644
--- a/Changes
+++ b/Changes
@@ -11,6 +11,10 @@ for, noteworthy changes.
         an instance of the class. This should alleviate some frustrating
         forgot-to-load-my-type bugs. rt.cpan.org #44639 (Sartak)
 
+    * Moose::Meta::Role::Application::ToClass
+      - Revert the class-overrides-role warning in favor of a solution outside
+        of the Moose core (Sartak)
+
 0.75_01 Thu, April 23, 2009
     * Moose::Meta::Role::Application::ToClass
       - Moose now warns about each class overriding methods from roles it
diff --git a/lib/Moose/Manual/Delta.pod b/lib/Moose/Manual/Delta.pod
index 9cb3e26..3fc4180 100644
--- a/lib/Moose/Manual/Delta.pod
+++ b/lib/Moose/Manual/Delta.pod
@@ -18,25 +18,6 @@ send us a patch.
 
 =head1 Version 0.76
 
-L<Moose> now warns about a class overriding methods from roles it
-consumes. This warning is useful for discovering I<accidental> name
-collisions, which is part of why using roles is much less painful than
-multiple inheritance. You can silence this warning by explicitly
-excluding methods you override from roles. For example,
-
-    package Role;
-    sub foo { "Default role implementation" }
-
-    package Class;
-    with 'Role' => { excludes => 'foo' };
-    sub foo { "Overriding class implementation" }
-
-Since this warning has been decried by some (such as chromatic in
-L<http://www.modernperlbooks.com/mt/2009/04/the-value-of-a-warning.html>),
-we ask that you provide feedback about whether this warning has helped or
-hindered you. If it turns out to have been a bad idea, we will not
-hesitate to remove it from future versions.
-
 Type constraints no longer run coercions for a value that already matches the
 constraint.  This may affect some (arguably buggy) edge case coercions that
 rely on side effects in the C<via> clause.