This is an automated email from the git hooks/post-receive script.

gregoa pushed a commit to branch master
in repository libmoo-perl.

commit 2fe5508ab0fd943fe4a2844cda97349d1e09d3e0
Author: Matt S Trout <>
Date:   Tue Sep 6 07:07:34 2016 -0400

    clarify documentation of meta method
 Changes    | 2 ++
 lib/ | 9 +++++++--
 2 files changed, 9 insertions(+), 2 deletions(-)

diff --git a/Changes b/Changes
index 7399840..5c6e03c 100644
--- a/Changes
+++ b/Changes
@@ -1,5 +1,7 @@
 Revision history for Moo
+  - clarify meta method documentation
 2.002004 - 2016-06-28
   - fixed another case of local functions interfering with generated code.
diff --git a/lib/ b/lib/
index 5ec4f07..e580693 100644
--- a/lib/
+++ b/lib/
@@ -442,8 +442,13 @@ superclasses.
   my $meta = Foo::Bar->meta;
   my @methods = $meta->get_method_list;
-Returns a L<Moose metaclass|Moose::Meta::Class> object for the class.  The
-metaclass will only be built on demand, loading Moose in the process.
+Returns an object that will behave as if it is a
+L<Moose metaclass|Moose::Meta::Class> object for the class. If you call
+anything other than C<make_immutable> on it, the object will be transparently
+upgraded to a genuine L<Moose::Meta::Class> instance, loading Moose in the
+process if required. C<make_immutable> itself is a no-op, since we generate
+metaclasses that are already immutable, and users converting from Moose had
+an unfortunate tendency to accidentally load Moose by calling it.

Alioth's /usr/local/bin/git-commit-notice on 

Pkg-perl-cvs-commits mailing list

Reply via email to