From: Jesse Luehrs <doy@tozt.net>
Date: Thu, 5 May 2011 15:33:14 +0000 (-0500)
Subject: mention duck_type in ::Manual::Types
X-Git-Tag: 2.0003~61
X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=c49308d9a100ada279d540f7e1630f467f3c3092;p=gitmo%2FMoose.git

mention duck_type in ::Manual::Types
---

diff --git a/lib/Moose/Manual/Types.pod b/lib/Moose/Manual/Types.pod
index cd0dde6..1b7d873 100644
--- a/lib/Moose/Manual/Types.pod
+++ b/lib/Moose/Manual/Types.pod
@@ -318,9 +318,7 @@ coercion might be a better answer.
 For our example above, we might want to be more specific, and insist
 that output be an object with a C<print> method:
 
-  subtype 'CanPrint'
-      => as 'Object'
-      => where { $_->can('print') };
+  duck_type 'CanPrint', [qw(print)];
 
 We can coerce file handles to an object that satisfies this condition
 with a simple wrapper class:
@@ -360,8 +358,8 @@ make your class internals simpler.
 
 The L<Moose::Util::TypeConstraints> module exports a number of helper
 functions for creating specific kinds of types. These include
-C<class_type>, C<role_type>, and C<maybe_type>. See the docs for
-details.
+C<class_type>, C<role_type>, C<maybe_type>, and C<duck_type>. See the
+docs for details.
 
 One helper worth noting is C<enum>, which allows you to create a
 subtype of C<Str> that only allows the specified values: