[TypeInfo] Fix type resolution when called class is in other namespace#62997
Merged
Conversation
24f895a to
84f109a
Compare
stof
reviewed
Jan 8, 2026
84f109a to
65bf8ed
Compare
Member
|
Thank you @mtarld. |
This was referenced Jan 24, 2026
Merged
Merged
Merged
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
4 participants
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.
When resolving
staticreturn type for a child class in a different namespace than the parent class where the method is declared, the wrong namespace was used.The fix adds the called class to the uses array when its namespace differs from the declaring class, allowing
normalize()to resolve it correctly.