Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Implement Perl-compatible restricted-hash semantics

Offen
  • Stimmt etwas nicht?
#1,502 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
45/100
Issue-Typ
Feature
Klarheit
Klar beschrieben
Aktivitätsstatus
Aktiv
Tech-Stack
java, perl
Bereich
backend, compilers

Rechercherichtung

The issue is about implementing restricted-hash semantics in Hash::Util for both JVM and interpreter backends. Start by examining the existing Hash::Util module code in the PerlOnJava repository, likely in lib/Hash/Util.pm or similar. Review the failing tests in dev/tools/feature-audit/remaining_semantics.t and the CPAN test failures from MooX::Params::CompiledValidators. Understand Perl's native behavior by testing the reproduction script with a standard Perl interpreter. The work involves modifying core hash operations across two backends, so familiarity with the project's internals is essential. Done means the reproduction script behaves like native Perl and the existing audit tests pass.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

bug enhancement

Summary

Implement Perl-compatible restricted-hash semantics for Hash::Util on both the JVM and interpreter backends.

Current behavior

The bundled Hash::Util exposes several restricted-hash APIs, but key-locking is a no-op and the remaining operations are only partially implemented:

  • lock_keys and unlock_keys are registered but do not change hash behavior.
  • lock_value and unlock_value are compatibility no-ops.
  • lock_keys_plus is a no-op.
  • lock_hash prevents some writes, but does not reject reads of missing keys and does not consistently reproduce Perl's restricted-hash diagnostics.
  • Inspection helpers such as hash_locked and hash_unlocked return placeholder values.

The feature matrix currently marks restricted hashes unsupported. docs/reference/bundled-modules.md should also be reconciled because it currently lists Hash::Util as providing lock_keys and lock_hash without describing the partial semantics.

Reproduction

use Hash::Util qw(lock_keys lock_hash);

my %keys = (a => 1);
lock_keys(%keys, 'a');
my $added = eval { $keys{b} = 2; 1 };
my $read  = eval { my $value = $keys{b}; 1 };

my %hash = (a => 1);
lock_hash(%hash);
my $missing = eval { my $value = $hash{b}; 1 };

Native Perl rejects the disallowed-key operations. PerlOnJava currently allows the lock_keys add/read operations and the lock_hash missing-key read on both backends.

Compatibility evidence

CPAN distribution MooX::Params::CompiledValidators v0.05 failed 3 of 17 tests under PerlOnJava in run 20260922-180448-60378:

  • t/010-basic.t: restricted-hash access was not rejected.
  • t/020-moose.t: restricted-hash access was not rejected.

Under system Perl, those two test files pass. The third file has an unrelated warning-sensitive Type::Tiny serialization failure.

The smallest direct probe also reproduces the backend gap: native Perl reports Attempt to access disallowed key, while both JVM and interpreter return without an error.

Proposed scope

  • Implement key restrictions and enforcement for read, write, delete, and key creation.
  • Implement whole-hash and value locking/unlocking with Perl-compatible state transitions.
  • Implement lock_keys_plus and inspection helpers with correct results.
  • Match Perl's relevant error behavior where practical.
  • Add project-owned unit tests covering both backends and validate expected behavior with standard Perl.
  • Update the bundled-modules documentation to distinguish implemented APIs from partial/no-op compatibility shims.

References

  • dev/tools/feature-audit/remaining_semantics.t already records restricted-hash enforcement as failing on both backends.
  • dev/design/feature-audit-plan.md records this as a known unsupported gap.
Vorherrschende Sprache
Perl
Sterne
64
Forks
7
Ø Merge
5 Std. 31 Min.
Gemergte PRs (30 T.)
214

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus fglock/PerlOnJava

Alle Issues in fglock/PerlOnJava

Ähnliche Issues

Weitere Issues zu Perl

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.