Uh oh!
There was an error while loading. Please reload this page.
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
commented
Nov 28, 2019
(rust_highfive has picked a reviewer for you, use r? to override) |
rust-highfive
commented
Nov 28, 2019
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 |
the8472
commented
Nov 28, 2019
Would it make sense to compute the distance over skeletons instead of looking either at the regular distance or the exact skeleton match? |
estebank
commented
Nov 28, 2019
@the8472 that's a good idea. |
petrochenkov
commented
Nov 30, 2019
Tidy fails because the new crates.io dependencies are not whitelisted. |
petrochenkov
commented
Nov 30, 2019
+1 Also, it looks like it can be an implementation details of |
bors
commented
Dec 3, 2019
☔ The latest upstream changes (presumably #66997) made this pull request unmergeable. Please resolve the merge conflicts. |
joelpalmer
commented
Dec 9, 2019
Ping from Triage: any updates @estebank? |
joelpalmer
commented
Jan 6, 2020
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