Emit constant-subroutine redefinition warning for equal cached values
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 55/100
Research direction
Start by reading RuntimeGlob and tracing isSameCachedConstant through the wrapper identity and cached scalar value checks. Add project owned regression coverage for the reported redefinition and same wrapper re-export cases, and first verify the expected warning behavior with standard Perl. Done means one warning on both PerlOnJava backends for replacement by a distinct wrapper with an equal cached value, and no spurious warning when re-exporting the same wrapper.
Written by the indexing model from the issue text.
Description
Summary
PerlOnJava misses Perl's constant-subroutine redefinition warning when a newly installed constant wrapper has the same cached return value as the previous wrapper.
Evidence
The Constant-Export-Lazy 0.17 test suite passed all 123 tests under system Perl 5.42.2. In CPAN random-tester run 20261116-130945-12232, PerlOnJava failed 2 of 15 assertions in t/private_name_munger.t on both the JVM and interpreter backends.
The test imports BLAH once, changes the private-name mapping, and imports BLAH again. It expects one warning matching Constant subroutine main::BLAH redefined; PerlOnJava reports no warning. The other assertions in the test pass.
Investigation clue
RuntimeGlob suppresses a redefinition warning when isSameCachedConstant considers the old and new constant wrappers equivalent by their cached scalar values. This case suggests that equal returned values do not make distinct constant subroutine definitions equivalent for Perl's redefinition-warning behavior. Please verify the wrapper identity and cached-value path while fixing it.
Acceptance criteria
- The focused behavior emits one
Constant subroutine main::BLAH redefinedwarning on both PerlOnJava backends. - Re-exporting the same constant wrapper without replacing its definition does not introduce a spurious warning.
- Add project-owned regression coverage and validate its standard Perl behavior before using it to drive the fix.
- Dominant language
- Perl
- Stars
- 67
- Forks
- 8
- Avg merge
- 5h 12m
- Merged PRs (30d)
- 131
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from fglock/PerlOnJava
-
area:cpan-port bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
fglock/PerlOnJava#2153 ·
Maintainers usually reply within 1 day
-
area:cpan-port area:parser bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
fglock/PerlOnJava#2137 ·
Maintainers usually reply within 1 day
-
area:backend area:cpan-port area:runtime bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
fglock/PerlOnJava#2071 ·
Maintainers usually reply within 1 day
-
area:runtime documentation enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
fglock/PerlOnJava#1579 ·
Maintainers usually reply within 1 day
-
area:cpan-port bug
Difficulty 3/5 1-2 days Newbie friendliness 62/100
fglock/PerlOnJava#2157 ·
Maintainers usually reply within 1 day
All issues in fglock/PerlOnJava
Similar issues
-
Dev-output directory preparation accepts file-valued lib/include paths and fails on dangling linksOpenteam-cli
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
-
Difficulty 1/5 Under an hour Newbie friendliness 93/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
inverse-inc/packetfence#9728 ·
Maintainers usually reply within 1 day
-
fix(char-create): show the real reason a character is refusedPossibly taken @baphomello claimed this 1 day ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day