Aiui the most salient feature of your new type is being syntax sugar
for conveniently creating and naming a sum type that includes `Failure`,
i.e. instead of:
my $foo where Int | Failure;
$foo = 42;
$foo = Failure;
$foo = 'nope'; # Type check failed in assignment to $foo; expected
Not sure what you mean by 'leaking into CORE', but I wouldn't use Metamodel::
namespace too. My suggestion would be to use Type::SumHOW or
Type::Metamodel::SumHOW. The latter is better from namespace structuring point
of view unless long names disgust you.
Best regards,
Vadim Belman
> On Apr 8
I wrote a small sum type module that subclasses
Perl6::Metamodel::SubsetHOW. I was thinking of naming it either
Type::Sum or Metamodel::SumHOW, but Type::Sum doesn't follow the style
Rakudo uses for naming MOP classes, and Metamodel::SumHOW may not be a
good name because it'd leak the module in
