fix nested call regression in generic bodies #22189
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.
fixes #22187
What was done for
tyGenericParam
arguments in calls in generic bodies in #22029 is now done fortyFromExpr
parameters. The "fauxMatch" mechanism seems to have been in place for something like this but it made things more confusing than it had to be in this case, at least I can't see the need for it in the current state, so just skip it fortyUnknown
(=tyFromExpr
apparently) and use the failing overload fallback.