avoid SpecifiedTypes allocation in setRootExpr when unchanged#5326
Closed
SanderMuller wants to merge 1 commit intophpstan:2.1.xfrom
Closed
avoid SpecifiedTypes allocation in setRootExpr when unchanged#5326SanderMuller wants to merge 1 commit intophpstan:2.1.xfrom
SanderMuller wants to merge 1 commit intophpstan:2.1.xfrom
Conversation
Collaborator
|
You've opened the pull request against the latest branch 2.2.x. PHPStan 2.2 is not going to be released for months. If your code is relevant on 2.1.x and you want it to be released sooner, please rebase your pull request and change its target to 2.1.x. |
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
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.
Problem
SpecifiedTypes::setRootExpr()is called on the return value of nearly everyspecifyTypesInCondition()call inTypeSpecifier. Each call allocates a newSpecifiedTypesobject, even when the root expression is already the same object.Since
specifyTypesInConditionrecurses through the AST and callssetRootExpr($expr)at each level, inner calls often set the root to a node that an outer call then overwrites with the same node again. The sameExprobject reference is passed down and back up the call chain, so identity (===) is the right check here.Solution
Impact
CI benchmark results to follow.