-
Notifications
You must be signed in to change notification settings - Fork 17.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
x/tools/gopls: prioritise explicit upper case matches in completion results #64224
Comments
Thanks for the report. I think you're right: we should update our fuzzy matcher to prefer exact case match. This is a gopls issue, so transferring to the gopls issue tracker. |
There is a bonus for case sensitive match already here. I think the problem is we use the same bonus for matching the first letter of a segment, so the match bonus doesn't differentiate the case in this issue. It might work to just split those apart into separate bonuses. |
Change https://go.dev/cl/592519 mentions this issue: |
In the general case I can see why case-insensitive completion makes sense, but if I've explicitly provided an upper case letter I would expect it to prioritise exact matches.
What's even stranger is that without entering any text at all,
Name
is the first option:The text was updated successfully, but these errors were encountered: