-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Improve documentation search fuzziness #34454
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
Comments
1 is a duplicate of #22786 |
@steveklabnik Thanks, I narrowed the issue a bit. Another example that brought me back here: searching for 'http' returns several results! ...for P.S. I still don't get what the search bar's |
You can quote the word if you don't want fuzzy search. (broken on stable though) |
Type |
Ah, that explains the 'S' too. I wouldn't have tried them outside of the text box, because the hints were inside the text box. Cool, though! |
Triage: the current rustdoc search uses basic Levenshtein edit distance when looking for items in the search index, with a maximum distance of 3 (unless the search term is a substring of the result). I'm not totally sure of other advances in fuzzy test searching, but if they can be implemented in JavaScript, we can certainly give them a shot. |
I'd love to see better searching.
Besides the lack of search for the book itself,Search filters out some characters without telling you; e.g.C++
and[Unstable]
are reasonable search terms, but the first gives false positives by usingC
and the second isn't indexed?Related: the search box says that
?
gives more options, but it just lists everything like a wildcard.The text was updated successfully, but these errors were encountered: