Skip to content

Stop spelling suggestions after 10 name-not-found errors #16174

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

Merged
merged 1 commit into from
May 31, 2017

Conversation

sandersn
Copy link
Member

Spelling suggestions now stop after the tenth name-not-found error, which is better for performance.

Previously, spelling suggestions stopped after name-not-found errors led to 10 suggestions. This may never happen for a failed import, which is the most common case for lots of name-not-found errors. In that worst case, we would continue to search for spelling suggestions for every name-not-found error but never find any.

Previously, spelling suggestions stopped after name-not-found errors led
to 10 *suggestions*. This may never happen for a failed import, which is
the most common case for lots of name-not-found errors. Now spelling
suggestions stop after the 10th name-not-found errors, which is better
for performance.
@sandersn sandersn merged commit b8d39d7 into master May 31, 2017
@sandersn sandersn deleted the max-10-errors-for-suggestions branch May 31, 2017 16:45
@microsoft microsoft locked and limited conversation to collaborators Jun 14, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants