-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Account for unicode confusables on typoed identifiers #66849
Conversation
When a name can't be matched to any existing identifier, we look for identifiers that have the same "skeleton" for possible suggestions, instead of relying only on Levenshtein distance.
(rust_highfive has picked a reviewer for you, use r? to override) |
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
Would it make sense to compute the distance over skeletons instead of looking either at the regular distance or the exact skeleton match? |
@the8472 that's a good idea. |
Tidy fails because the new crates.io dependencies are not whitelisted. |
+1 Also, it looks like it can be an implementation details of |
☔ The latest upstream changes (presumably #66997) made this pull request unmergeable. Please resolve the merge conflicts. |
Ping from Triage: any updates @estebank? |
Ping from Triage: Closing due to inactivity. Please re-open with updates. Thanks! @estebank |
When a name can't be matched to any existing identifier, we look for
identifiers that have the same "skeleton" for possible suggestions,
instead of relying only on Levenshtein distance.
CC #55467