On Tue, Sep 8, 2009 at 9:32 AM, Hans Dieter Pearcey <[email protected]> wrote:
> Whenever we've talked about coring MooseX modules, it's mostly been MXAH
> and
> MooseX::Types. Does anyone have any changes they'd like to see in
> MX::Types
> before it becomes, say, Moose::Types? (Moose::TypeConstraints?)
>
> For myself:
>
> * Warn/die on subtype DeclaredType => as Foo => where { ... } (accidental
> stringification) -- I thought someone had fixed this, but it came up as a
> silent failure recently, so maybe not in all cases?
>
> * Standardize on a best practice for parameterized non-global types (e.g.
> ArrayRef[MyObject] vs. ArrayRefOfMyObject) and make documentation use it
> consistently
> * if the former, the RT bug about coercions needs to be fixed
>
> * smarter renaming of imports -- e.g. if you try to import Foo from a type
> library, with -prefix => 'My', it'd really be nice to get to_MyFoo and
> is_MyFoo helpers instead of Myto_Foo and Myis_Foo
>
> * MooseX::Types::Moose -> Moose::Types::Native (maybe)
>
> * Should Structured be included?
>
> hdp.
>
+1 for Types w/o Moose.
But back on the original topic, something that bothers me about MX::Types is
that you can't have : in a type name. I mostly use that for signature stuff
in catch blocks w/ TryCatch. Although I guess the existent Moose types
system allows for : in the names so maybe the inclusion would resolve that
issue.
--
fREW Schmidt
http://blog.afoolishmanifesto.com
