Fix Set::Scalar 1.29 parser and overloaded set-operation failures

Abierto
#2,074 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
java, perl

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

area:backend area:cpan-port area:parser area:runtime blocked:ownership bug

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:

  1. t/intersection.t fails 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(".

  2. t/laws.t exits at its second property check, DeMorgan -+. It reports got (), 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 in t/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.t passes on JVM and interpreter, including its final indirect method-call expression.
  • t/laws.t passes 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.t parse failure; t/laws.t De Morgan failure.
  • Focused interpreter reruns: same two failures.
Lenguaje dominante
Perl
Estrellas
67
Forks
8
Merge medio
5 h 12 min
PR fusionados (30 d)
131

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de fglock/PerlOnJava

Todos los issues de fglock/PerlOnJava

Issues similares

Más issues de Perl

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.