[ty] Avoid secondary tree traversal to get call expression for keyword arguments #19429
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.
Summary
Follow up to https://github.com/astral-sh/ruff/pull/19417/files#r2215520292
Extract the enclosing
CallExprwhen resolving theKeywordArgumentgoto target (where we have access to the ancestor chain)instead of doing another tree traversal.
Not only is this faster. It's also less confusing (I assumed that there was more to it then just picking the parent call expression because it did use a second traversal).
Test Plan
cargo test