Regression: ArrayObject::getIteratorClass() — var_export after setIteratorClass() returns __set_state (re-#10778, ext/spl/spl_array.c)

Problem

#10778 was closed, but the compliance guard regressed: when setIteratorClass() is called as a void prelude immediately before var_export($ao->getIteratorClass(), true) in the same statement block, the compiler wires the wrong value into var_export and prints an ArrayObject::__set_state dump instead of the iterator class name string.

Repro	Zend 8.2+	VM (2026-07-06)
`var_export($ao->getIteratorClass(), true)` after `$ao->setIteratorClass('ArrayIterator')`	`'ArrayIterator'`	`'\\ArrayObject::__set_state(array())'`
Direct `$ao->getIteratorClass()` without preceding void call in expr	`'ArrayIterator'`	`'ArrayIterator'` (see `arrayobject_iterator_class.phpt`)

php-src reference

php/php-src ext/spl/spl_array.c — spl_array_getIteratorClass / spl_array_setIteratorClass

PHP implementation target

lib/Compiler.php — sibling void MethodCall prelude dropping before inline var_export arg (Stdlib: ArrayObject::getIteratorClass() returns null after void setIteratorClass() in expression (ext/spl/spl_array.c) #10778, Regression: PATH_SEPARATOR empty in VM-compiled scripts — explode() ValueError (re-#11444, ext/standard/basic_functions.c) #15833 patterns); do not add C in runtime/
ext/spl/ArrayObjectBuiltin.php / ext/spl/SplArrayStorage.php — runtime semantics already correct for direct calls

Repro

./script/docker-exec.sh -- bash -lc 'source script/php-env.sh && php bin/vm.php test/repro/maintainer_gap_arrayobject_getiterator_after_set.php'
./script/docker-exec.sh -- bash -lc 'source script/php-env.sh && vendor/bin/phpunit test/compliance/VMTest.php --filter arrayobject_getiterator_after_set'

Done when

test/repro/maintainer_gap_arrayobject_getiterator_after_set.php prints 'ArrayIterator'
test/compliance/cases/stdlib/arrayobject_getiterator_after_set.phpt green in VMTest
test/unit/ArrayObjectGetIteratorAfterSetTest.php green if applicable
php-src-strict; no php-compiler-strict shortcut

claim: cursor-agent-lane-c — starting this run

Compiler: fix var_export after void setIteratorClass inline arg (#16794…

Merged via #16803

Root cause: resolveSiblingInlineCallArgProducerSlot mapped var_export arg #0 to the first FUNCCALL_EXEC_RETURN slot (the ArrayObject ctor) before compiling the hoisted getIteratorClass() MethodCall.

Fix: compile hoisted MethodCall/StaticCall sibling producers and wire via operand slots; extend var_export arg-#0 matching for MethodCall producers.

Verification (green):

./script/docker-exec.sh -- bash -lc 'source script/php-env.sh && php bin/vm.php test/repro/maintainer_gap_arrayobject_getiterator_after_set.php'
./script/docker-exec.sh -- bash -lc 'source script/php-env.sh && vendor/bin/phpunit test/unit/ArrayObjectGetIteratorAfterSetTest.php'
./script/docker-exec.sh -- bash -lc 'source script/php-env.sh && vendor/bin/phpunit test/compliance/VMTest.php --filter arrayobject_getiterator_after_set'

Navigation Menu

Repository navigation

Regression: ArrayObject::getIteratorClass() — var_export after setIteratorClass() returns __set_state (re-#10778, ext/spl/spl_array.c) #16794

Category

Problem

php-src reference

PHP implementation target

Repro

Done when

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Regression: ArrayObject::getIteratorClass() — var_export after setIteratorClass() returns __set_state (re-#10778, ext/spl/spl_array.c) #16794

Description

Category

Problem

php-src reference

PHP implementation target

Repro

Done when

Activity

PurHur commented on Jul 6, 2026

PurHur commented on Jul 6, 2026

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions