Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Project call-target narrowings through stored booleans #5528
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Uh oh!
There was an error while loading. Please reload this page.
Project call-target narrowings through stored booleans #5528
Changes from 1 commit
8b7330db3f4b84File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
Extends the conditional-expression machinery used for assignments like `$ok = $x->foo() !== null` so the narrowing survives through a later `if ($ok) { … }`. Previously only Variable/PropertyFetch/ArrayDimFetch/FuncCall sure-type targets were projected, so method calls (and static/nullsafe calls) were dropped entirely. For call-typed sure-type targets (FuncCall, MethodCall, NullsafeMethodCall, StaticCall) we only project when the sure-type expression is a sub-expression of the assigned RHS — not the RHS itself. That keeps the narrowing of `$x->foo()` in `$ok = $x->foo() !== null` while dropping the falsey-scalar loop's `$this->nullable() === null` projections that would wrongly survive across subsequent reassignments. PHPStan virtual nodes (e.g. NativeTypeExpr), scalars and const-fetches are rejected to avoid numeric-string array-key autocast and internal nodes leaking into the conditional-expression map. Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing