Fix Set::Scalar 1.29 parser and overloaded set-operation failures
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
Start with the named upstream reproductions, t/intersection.t at line 99 and the DeMorgan -+ check in t/laws.t; inspect issue #1429 and PR #1804 for related indirect dispatch work. Trace the parser path for the constructor/method expression and the overloaded operator behavior on both backends. Done means project regressions pass on both backends and the complete Set::Scalar 1.29 suite passes.
Written by the indexing model from the issue text.
Description
Summary
Set::Scalar 1.29 fails two upstream tests under PerlOnJava, while the complete suite passes under system Perl. The failures reproduce on both the JVM and interpreter backends and expose separate parser and runtime compatibility gaps.
Reproduction
Run the Set::Scalar 1.29 test suite (DAVIDO/Set-Scalar-1.29.tar.gz). The failures are:
-
t/intersection.tfails to compile at line 99 on this valid Perl expression:new Set::Scalar \$1,\$2,\$3,->intersection( new Set::Scalar \$2,\$3,\$4 )PerlOnJava reports
syntax error ... near "intersection(". -
t/laws.texits at its second property check,DeMorgan -+. It reportsgot (), expected (d e f g)for-($x + $y)versus-$x * -$y.
Both failures reproduce with the JVM and interpreter backends. The laws failure happens immediately, so the remainder of the property suite does not run under PerlOnJava.
Expected result
System Perl 5.42.2 passes all 22 test programs and 2,652 tests in the distribution's normal make test run.
PerlOnJava should accept the indirect constructor/method-call syntax and preserve Set::Scalar's complement, union, and intersection behavior so both tests pass on both backends.
Actual result
The archived PerlOnJava run reports:
Failed 2/22 test programs. 0/254 subtests failed.
t/intersection.t emits no TAP because parsing stops at line 99. t/laws.t emits its plan, then exits after the first failed law check. Focused reruns reproduce each failure on both backends.
Root-cause areas
These appear to be two independent PerlOnJava defects:
- Parser: the parser does not accept the
new Class ... ,->method(...)indirect method form used int/intersection.t. - Runtime/operator dispatch: the overloaded set expressions in the De Morgan check produce unequal results (
()versus(d e f g)). Investigate overloaded unary negation combined with overloaded+and*, including operand/result handling across both backends.
The first failure is related to #1429, which covered indirect-object dispatch used by Set::IntSpan and was resolved by PR #1804. Set::Scalar exercises a different constructor-plus-method expression shape, so this remains additional regression coverage. No existing issue for the De Morgan failure was found in the focused search.
Acceptance criteria
t/intersection.tpasses on JVM and interpreter, including its final indirect method-call expression.t/laws.tpasses all 2,375 property checks on JVM and interpreter.- Add project-owned regressions for both the indirect constructor/method-call syntax and the failing overloaded set identity.
- Validate any new project unit tests with system Perl before relying on them.
- The complete Set::Scalar 1.29 suite passes on both PerlOnJava backends.
Evidence
- CPAN random tester run:
20261116-130945-12232. - Distribution:
Set-Scalar-1.29(pure Perl; no XS/native dependency). - System Perl: PASS, 22 files / 2,652 tests.
- PerlOnJava archived run: FAIL, 2 of 22 programs.
- Focused JVM reruns:
t/intersection.tparse failure;t/laws.tDe Morgan failure. - Focused interpreter reruns: same two failures.
- 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