Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Method lookup still finds a subroutine after Symbol::Util delete_sub

Abierto
  • ¿Algo no está bien?
#1,610 1 comentario 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
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
68/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
perl
Área
compilers

Línea de trabajo

Start with the upstream t/50delete_sub.t test, especially test 23, and reproduce it under standard Perl to confirm the expected result. Trace the method lookup and symbol-table deletion paths, then add a project-owned regression covering delete_sub on both JVM and interpreter backends. Done means the focused regression and unchanged Symbol-Util 0.0203 test pass on both backends.

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

Descripción

area:runtime bug

Summary

After Symbol::Util::delete_sub removes a subroutine from the main package, PerlOnJava can still dispatch that subroutine as a class method. This breaks Perl's method lookup semantics: deleting main::FOO should make main->FOO unavailable, while unrelated calls through the remaining symbol table continue to work.

This is a pure-Perl compatibility failure, reproducible on both PerlOnJava execution backends. The unchanged upstream test passes under system Perl.

Reproduction

The failure is from Symbol-Util 0.0203, t/50delete_sub.t, test 23 (main->FOO is ok [2]). The relevant upstream sequence is:

use Symbol::Util 'delete_sub';

*FOO = sub { "code" };

# The method is initially available.
my $before = eval { main->FOO };

# Remove the CODE slot for main::FOO.
delete_sub("::FOO");

# Expected: method lookup fails, so the eval result is undefined.
my $after = eval { main->FOO };

Expected behavior under Perl: defined $after is false. On PerlOnJava, the upstream assertion ok(! defined eval { main->FOO }, 'main->FOO is ok [2]') fails, indicating that method dispatch still finds a defined result after deletion.

Evidence

  • CPAN random tester run: 20261002-095841-54171
  • Distribution: Symbol-Util 0.0203 (pure Perl)
  • Failing test: t/50delete_sub.t, assertion 23 of 24
  • Full PerlOnJava suite result: 306/307 assertions passed; 1/8 test programs failed
  • System Perl: all 307 assertions across 8 test programs passed in the archived oracle run; the focused t/50delete_sub.t also passes independently
  • PerlOnJava JVM backend: focused test fails at assertion 23
  • PerlOnJava interpreter backend: same focused assertion fails
  • Regression record: last known pass date 2026-09-12 at commit 141cdae65
  • Reproduced in current checkout at commit 0d3f46e4524573d58dd4ae91565f6de2d8b79435
  • Environment: macOS 26.6.2, Temurin OpenJDK 24.0.2, system Perl 5.42.2

The archived failing log also prints closedir() attempted on handle $GEN4 ... during CPAN configuration, but the target completed its tests and reported one ordinary assertion failure. The system-Perl oracle passed, and the focused failure reproduces directly on both backends, so that warning does not explain this result.

Expected behavior

Once delete_sub("::FOO") removes main::FOO's CODE slot, a subsequent main->FOO lookup must fail on both execution backends. The method lookup path must reflect the current package symbol table after this mutation.

Related issues

  • #1119 covers earlier Symbol::Util package-stash and typeglob-slot failures. Its report says subroutine deletion passed; this CPAN run records a later regression in that behavior.
  • #1523 covers method loss after a package stash is copied back. It is related to method dispatch after symbol-table mutation, but this report concerns stale successful lookup after delete_sub removes a method.

Suggested acceptance criteria

  • Add a focused project-owned regression test for method lookup after delete_sub removes a named CODE slot.
  • Validate the test with standard Perl before using it as a PerlOnJava regression test.
  • Confirm the test passes on both JVM and interpreter backends.
  • Confirm the unchanged Symbol-Util 0.0203 t/50delete_sub.t test passes.
Lenguaje dominante
Perl
Estrellas
64
Forks
7
Merge medio
5 h 13 min
PR fusionados (30 d)
181

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.