CPAN::Groonga

\nplan skip_all => "$m needed for this test" if \$@;};
}

for my $m (qw(Types::Serialiser JSON::PP Cpanel::JSON::XS)) {
    for (qw(t/02-basic.t t/03-is-bool.t t/04-to-bool.t)) {
        my $t = file(

al reasons, alias *Data::Bool::Impl with JSON::PP::Boolean
    *Data::Bool::Impl:: = *JSON::PP::Boolean::;

    # JSON/PP/Boolean.pm is redundant
    $INC{'JSON/PP/Boolean.pm'} ||= __FILE__
      unle

type hierarchies, etc.

A solution for that was adopted for JSON modules
around 2012 by using references to C<1> or C<0>
blessed into L<JSON::PP::Boolean> which was chosen
as the canonical package for

 these objects.

The problem with that was the coupling with L<JSON::PP>
for no apparent good reason. Booleans are independent
of JSON and this association makes little sense
when loading documents in

c Lehmann's L<Types::Serialiser> approached this problem
by creating a common interface used by L<JSON::XS> and L<CBOR::XS>
modules. This module lifts this core concept (including
idea, implementation