Allow an infer type node to resolve its own name #40483
Merged
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.
infer Xnormally makesXavailable in an adjacent scope - namely the containing conditional'struebranch. However, typically, a declaration should be capable of resolving to its own name. With this change, resolvingXwithin the context ofinfer X, will actually result inX's symbol, rather than anundefined(or, more confusingly, an outer scope) result.Fixes #40362