Moo is a light-weight object oriented programming framework which aims to be compatible with Moose. It does this by detecting when Moose has been loaded, and automatically "inflating" its classes and roles to full Moose classes and roles. This way, Moo classes can consume Moose roles, Moose classes can extend Moo classes, and so forth.

However, the surface syntax of Moo differs somewhat from Moose. For example the isa option when defining attributes in Moose must be either a string or a blessed Moose::Meta::TypeConstraint object; but in Moo must be a coderef. These differences in surface syntax make porting code from Moose to Moo potentially tricky. MooX::late provides some assistance by enabling a slightly more Moosey surface syntax.

String, Number, Counter and Bool are unlikely to ever be supported because of internal implementation details of Moo. If you need another attribute trait to be supported, let me know and I will consider it.

Five features. It is not the aim of MooX::late to make every aspect of Moo behave exactly identically to Moose. It's just going after the low-hanging fruit. So it does five things right now, and I promise that future versions will never do more than seven.

Previous releases of MooX::late added support for coerce => 1 and default => $nonref. These features have now been added to Moo itself, so MooX::late no longer has to deal with them.

Type constraint strings are interpreted using Type::Parser, using the type constraints defined in Types::Standard. This provides a very slight superset of Moose's type constraint syntax and built-in type constraints.

Any unrecognized string that looks like it might be a class name is interpreted as a class type constraint.