> 3) Type constraints decoupled from Moose and some things changed under the > hood to make it easier to improve error messages for things like > MX:T:Structured and other changes so that slurpy in MX:T:Structured doesn't > have to be an evil hack. A stand alone type constraint system that makes it > easier for me to complete the dependent and faceted type stuff sitting inthe > repo for like a year would be nice. And of course a sweet MooseX::Declare > style syntax. Then we can end the stringy types versus MooseX::Types style > types issue for good.
This would be godly. Moose::Util::TypeConstraints are confusing as hell for new people and increase the overall learning curve for Moose (because you so often find yourself needing MX::Types). String types should pull from core, and core types should be purposefully brittle so as to stop the use of string types. I'd also like to see a real mechanism to subtype coercions. Not being able to stack on coercions that limit size, remove padding, and unoverload a type at will really make for a bock of functionality that I find myself constantly implementing. I want some sort anonymous type coercion that I can expand TypeGenerator[ base => Str, trim => 'Both', unoverload => 1, lowercase => 1 ] -- Evan Carroll System Lord of the Internets http://www.evancarroll.com
