Acme-CPANModules-HashUtilities

 view release on metacpan or  search on metacpan

META.json  view on Meta::CPAN

         },
         {
            "class" : "Dist::Zilla::Plugin::ShareDir",
            "name" : "@Author::PERLANCAR/@Filter/ShareDir",
            "version" : "6.030"
         },
         {
            "class" : "Dist::Zilla::Plugin::MakeMaker",
            "config" : {
               "Dist::Zilla::Role::TestRunner" : {
                  "default_jobs" : 1
               }
            },
            "name" : "@Author::PERLANCAR/@Filter/MakeMaker",
            "version" : "6.030"
         },
         {
            "class" : "Dist::Zilla::Plugin::Manifest",
            "name" : "@Author::PERLANCAR/@Filter/Manifest",
            "version" : "6.030"
         },

META.yml  view on Meta::CPAN

      name: '@Author::PERLANCAR/@Filter/ExecDir'
      version: '6.030'
    -
      class: Dist::Zilla::Plugin::ShareDir
      name: '@Author::PERLANCAR/@Filter/ShareDir'
      version: '6.030'
    -
      class: Dist::Zilla::Plugin::MakeMaker
      config:
        Dist::Zilla::Role::TestRunner:
          default_jobs: 1
      name: '@Author::PERLANCAR/@Filter/MakeMaker'
      version: '6.030'
    -
      class: Dist::Zilla::Plugin::Manifest
      name: '@Author::PERLANCAR/@Filter/Manifest'
      version: '6.030'
    -
      class: Dist::Zilla::Plugin::ConfirmRelease
      name: '@Author::PERLANCAR/@Filter/ConfirmRelease'
      version: '6.030'

README  view on Meta::CPAN

    but sometimes you want different merging behavior, particularly in case
    where the same key is found in more than one hash. See the various hash
    merging modules:

    Hash::Merge

    Data::ModeMerge

    Hash::Union

  Providing default value for non-existing keys
    Hash::WithDefault

  Restricting keys
    Perl through Hash::Util (a core module) allows you to restrict what keys
    can be set in a hash. This can be used to protect against typos and for
    simple validation. (For more complex validation, e.g. allowing patterns
    of valid keys and/or rejecting patterns of invalid keys, you can use the
    tie mechanism.)

  Reversing (inverting)

lib/Acme/CPANModules/HashUtilities.pm  view on Meta::CPAN

the same key is found in more than one hash. See the various hash merging
modules:

<pm:Hash::Merge>

<pm:Data::ModeMerge>

<pm:Hash::Union>


## Providing default value for non-existing keys

<pm:Hash::WithDefault>


## Restricting keys

Perl through <pm:Hash::Util> (a core module) allows you to restrict what keys
can be set in a hash. This can be used to protect against typos and for simple
validation. (For more complex validation, e.g. allowing patterns of valid keys
and/or rejecting patterns of invalid keys, you can use the tie mechanism.)

lib/Acme/CPANModules/HashUtilities.pm  view on Meta::CPAN

but sometimes you want different merging behavior, particularly in case where
the same key is found in more than one hash. See the various hash merging
modules:

L<Hash::Merge>

L<Data::ModeMerge>

L<Hash::Union>

=head2 Providing default value for non-existing keys

L<Hash::WithDefault>

=head2 Restricting keys

Perl through L<Hash::Util> (a core module) allows you to restrict what keys
can be set in a hash. This can be used to protect against typos and for simple
validation. (For more complex validation, e.g. allowing patterns of valid keys
and/or rejecting patterns of invalid keys, you can use the tie mechanism.)