Repository navigation
Conversation
An assignment through a reference to a typed property coerces the value, so its result can differ from the assigned operand, but range inference copied the operand's range to the result. Reuse it only when the target is a CV that cannot be a reference.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Assigning through a reference to a typed property coerces the value, but range inference copied the assigned operand's range to the result, so
($GLOBALS['real'] = 9007199254740993) & 1with$GLOBALS['real']bound to a float property is folded to 1 instead of 0. The range is now reused only when the target is a CV that cannot be a reference. Split out of #24110.