Group
Extension

Matches 3

Moose ( D/DO/DOY/Moose-2.0604.tar.gz, DOY, 2012; MetaCPAN )
Moose/lib/Moose/Util/TypeConstraints.pm ( view source; MetaCPAN )
ndef'},
          => sub { die "I don't know what $_ is" }
      );
  }

Or a simple JSON serializer:

  sub to_json {
      my $x = shift;
      match_on_type $x => (
          HashRef => sub {
     
            . (
                  join ", " =>
                      map { '"' . $_ . '" : ' . to_json( $hash->{$_} ) }
                      sort keys %$hash
                  ) . ' }';
          },
o_json($_) } @$array ) . ' ]';
          },
          Num   => sub {$_},
          Str   => sub { '"' . $_ . '"' },
          Undef => sub {'null'},
          => sub { die "$_ is not acceptable json t
Moose ( D/DO/DOY/Moose-2.0604.tar.gz, FLORA, 2012; MetaCPAN )
Moose/lib/Moose/Util/TypeConstraints/OptimizedConstraints.pm ( view source; MetaCPAN )
mporary here because regex matching promotes an IV to a PV,
# and that confuses some things (like JSON.pm)
sub Int {
    my $value = $_[0];
    defined($value) && !ref($value) && $value =~ /\A-?[0-9]+
Moose ( D/DO/DOY/Moose-2.0604.tar.gz, DOY, 2012; MetaCPAN )
Moose/lib/Moose/Manual/Delta.pod ( view source; MetaCPAN )
all of the Moose extensions you use will continue to work.

The other part is that Moose's C<META.json> file will also specify the
conflicts under the C<x_conflicts> key. We are working with the Perl 

Powered by Groonga
Maintained by Kenichi Ishigaki <ishigaki@cpan.org>. If you find anything, submit it on GitHub.