Fix Set::Scalar 1.29 parser and overloaded set-operation failures
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Idoneità per principianti
- 35/100
Direzione di ricerca
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.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
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.
- Lingua principale
- Perl
- Stelle
- 67
- Fork
- 8
- Merge medio
- 5h 12m
- PR unite (30g)
- 131
Preparare l'ambiente
- Include un Dockerfile o un file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di fglock/PerlOnJava
-
area:cpan-port bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
fglock/PerlOnJava#2153 ·
I maintainer di solito rispondono entro 1 giorno
-
area:cpan-port area:parser bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
fglock/PerlOnJava#2137 ·
I maintainer di solito rispondono entro 1 giorno
-
area:backend area:cpan-port area:runtime bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
fglock/PerlOnJava#2071 ·
I maintainer di solito rispondono entro 1 giorno
-
area:runtime documentation enhancement
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
fglock/PerlOnJava#1579 ·
I maintainer di solito rispondono entro 1 giorno
-
area:cpan-port bug
Difficoltà 3/5 1-2 giorni Idoneità per principianti 62/100
fglock/PerlOnJava#2157 ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di fglock/PerlOnJava
Issue simili
-
Dev-output directory preparation accepts file-valued lib/include paths and fails on dangling linksApertateam-cli
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
I maintainer di solito rispondono entro 2 giorni
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 66/100
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 93/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 73/100
inverse-inc/packetfence#9728 ·
I maintainer di solito rispondono entro 1 giorno
-
fix(char-create): show the real reason a character is refusedForse già presa @baphomello l’ha presa 1 giorno fa. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
I maintainer di solito rispondono entro 1 giorno