From: Dave Rolsky <autarch@urth.org>
Date: Mon, 13 Sep 2010 15:27:55 +0000 (-0500)
Subject: Clarify that coerce requires a type constraint with a coercion
X-Git-Tag: 1.13~4
X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=2e953f1281bbaeebb3b956bd6dd25f8050c36a0c;p=gitmo%2FMoose.git

Clarify that coerce requires a type constraint with a coercion
---

diff --git a/lib/Moose.pm b/lib/Moose.pm
index 19d4482..20943af 100644
--- a/lib/Moose.pm
+++ b/lib/Moose.pm
@@ -474,9 +474,9 @@ for information on how to define a new type, and how to retrieve type meta-data)
 =item I<coerce =E<gt> (1|0)>
 
 This will attempt to use coercion with the supplied type constraint to change
-the value passed into any accessors or constructors. You B<must> have supplied
-a type constraint in order for this to work. See L<Moose::Cookbook::Basics::Recipe5>
-for an example.
+the value passed into any accessors or constructors. You B<must> supply a type
+constraint, and that type constraint B<must> defined a coercion. See
+L<Moose::Cookbook::Basics::Recipe5> for an example.
 
 =item I<does =E<gt> $role_name>