Bug #73765 for Moose: coerce doesn't create type constraints on type names

Thu Jan 05 10:54:03 2012 gbjk [...] thermeon.com - Ticket created

Subject:

coerce doesn't create type constraints on type names

Simple: perl -Moose -E'coerce "ArrayRef[Int]", from "Int", via { [$_] }' Cannot find type 'ArrayRef[Int]', perhaps you forgot to load it at /usr/local/lib/perl/5.10.1/Moose/Util/TypeConstraints.pm line 581 This is fixed with find_or_parse_type_constraint: perl -Moose - E'Moose::Util::TypeConstraints::find_or_parse_type_constraint("ArrayRef[I nt]");coerce "ArrayRef[Int]", from "Int", via { [$_] }'

Sun May 27 21:23:11 2012 DROLSKY [...] cpan.org - Correspondence added

On Thu Jan 05 10:54:03 2012, gbjk@thermeoneurope.com wrote: Show quoted text

> Simple: > > perl -Moose -E'coerce "ArrayRef[Int]", from "Int", via { [$_] }' > > Cannot find type 'ArrayRef[Int]', perhaps you forgot to load it at > /usr/local/lib/perl/5.10.1/Moose/Util/TypeConstraints.pm line 581 > > This is fixed with find_or_parse_type_constraint: > > perl -Moose - >

E'Moose::Util::TypeConstraints::find_or_parse_type_constraint("ArrayRef[ I Show quoted text

> nt]");coerce "ArrayRef[Int]", from "Int", via { [$_] }'

I'm not sure this is a bug. More importantly, the only cases where this would happen are when you try to create coercions on built-in parameterizable types, which is a really really bad idea. Instead, it's safer to create a subtype of ArrayRef[Int] and coerce to that. Regardless, this will all be fixed once we start using Type ;)

Sun May 27 21:23:12 2012 The RT System itself - Status changed from 'new' to 'open'

Wed Aug 28 21:15:04 2013 DOY [...] cpan.org - Correspondence added

Yeah, this isn't a bug.

Wed Aug 28 21:15:05 2013 DOY [...] cpan.org - Status changed from 'open' to 'rejected'