I'd split out type constraint definitions into a separate type library module. Here's a quick example:

use strict;
use warnings;

# thanks.pm is a shim for declaring multiple packages in the same file
+.
# It's on CPAN if you want it. Otherwise, just split them into separat
+e
# files.
no thanks qw(
    MyApp::Types
    MyApp::Printer
    MyApp::Printer::ThreeColour
    MyApp::Printer::FourColour
);

BEGIN {
    package MyApp::Types;
    use Type::Library -base, -declare => qw( ThreeColour FourColour );
    use Type::Utils;
    use Types::Standard -types;
    use Types::ReadOnly -types;
    
    declare ThreeColour, as Locked[
        Dict[
            cyan    => Optional[Num],
            magenta => Optional[Num],
            yellow  => Optional[Num],
        ]
    ], coercion => 1;
    
    # black is referred to as "key" in CYMK printing. presumably becau
+se
    # using a name that abbreviated to "B" would be confused with "blu
+e".
    declare FourColour, as Locked[
        Dict[
            @{ ThreeColour->parent->wrapped->parameters }, # voodoo?
            key => Optional[Num],
        ]
    ], coercion => 1;
};

BEGIN {
    package MyApp::Printer;
    use Moose::Role;
    
    # Let's assume the printer is only capable of printing one pixel.
    has pixel => (is => 'ro');
    
    sub dump {
        require Data::Dumper;
        Data::Dumper::Dumper(@_);
    }
};

BEGIN {
    package MyApp::Printer::ThreeColour;
    
    use MyApp::Types -types;
    
    use Moose;
    with qw(MyApp::Printer);
    
    has '+pixel' => (isa => ThreeColour, coerce => 1);
};

BEGIN {
    package MyApp::Printer::FourColour;
    
    use MyApp::Types -types;
    
    use Moose;
    with qw(MyApp::Printer);
    
    has '+pixel' => (isa => FourColour, coerce => 1);
};

my $printer = 'MyApp::Printer::FourColour'->new(
    pixel => { cyan => 9.4, magenta => 7, yellow => 4 },
);

print($printer->dump);

$printer->pixel->{key} = 9; # ok

print($printer->dump);

$printer->pixel->{black} = 6; # dies

[download]
use Moops; class Cow :rw { has name => (default => 'Ermintrude') }; say Cow->new->name

In reply to Re^3: constraining the keys of a HashRef in Moose by tobyink
in thread constraining the keys of a HashRef in Moose by tomgracey

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.