[ty] Fix out-of-order semantic token for function with regular argument after kwargs #21013
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
Fixes a bug where the semantic token provider returned out-of-order tokens for
function definitions with a regular parameter coming after a kwargs parameter:
The LSP specification isn't explicit whether out-of-order tokens are allowed, but
the way it reads suggests that providers are expected to return tokens in-order.
The root cause for this issue is that
Parameters::iter()only guarantees toreturn the parameters in source order if there are no syntax errors because of how
parameters are represented internally (different vectors for the different parameter kinds).
The ideal fix would be to change our
Parametersdefinition but that's a bit more work,which is why I decided to sort the parameters in place instead.
Fixes astral-sh/ty#1406
Test Plan
Added test