Repository navigation
Language: null default on non-nullable typed property fatal message — Zend suggests ?T (zend_compile.c) #31820
Description
Activity
claim: PHP Compiler Worker Lane B — starting this run (lane overflow: no eligible IR in lane B; stdlib/ext-owned queue skipped)
claim: Worker lane B — starting this run (lane overflow: no eligible IR in lane B; stdlib/ext-owned queue + named ext soap/imagick/sqlsrv skipped)
- added a commit that references this issue
on Aug 17, 2026 Follow-up merged: #31829
#31827 landed the Zend message text; #31829 upgrades presentation to
CompileFatal/PHP Fatal error:(file+line) so the CLI matches Zend’s fatal shape instead ofparseAndCompile failure:.Verification:
php bin/vm.php test/repro/maintainer_gap_null_default_typed_prop.php→ exit 255,PHP Fatal error: … Use the nullable type ?int …;./script/phpunit.sh --filter TypedPropNullDefaultFatal31820→ OK (4).
Category
Language:· php-src-strict · compile-time typed property defaultProblem
public int $x = null;(and other non-nullable typed properties defaulting tonull) must be a compile fatal. Zend’s message tells the user to use the nullable form; the compiler’sparseAndCompilefailure uses a shorter, different string.Probed 2026-08-17 — host Zend PHP 8.2 vs
php bin/vm.php.class T { public int $x = null; }Fatal error: Default value for property of type int may not be null. Use the nullable type ?int to allow null default valueparseAndCompile failure: … Cannot use null as default value for property $x of type intphp-src reference
Zend/zend_compile.c— typed property default null check / error message (“Use the nullable type ?%s …”)PHP implementation target
lib/Compiler.php/ property default type check — emit Zend’s fatal wording (include “Use the nullable type ?T …”)E_COMPILE_ERROR/ Fatal presentation used elsewhere for compile fatalsRepro
Done when
public T $prop = nullon non-nullableT(at leastint/string/float/bool/ class types)?int $x = nullstill accepted.phptguard undertest/compliance/cases/language/