Skip to content

Conversation

benlangmuir
Copy link
Contributor

If we won't show the diagnostics anyway, don't go to the trouble of
performing the typo-corrections, which can be expensive. This is really
helpful if there is a module import failure, which may cause many names
to fail to resolve and would otherwise trigger typo-correction.

We want to use it for indexing, but there is no good way to test it
there since indexing doesn't provide diagnostics, so at least make sure
it's tested somewhere.
The errors won't be captured in the response, and it can be expensive to
do typo-correction when there are many errors, which is common in
indexing.

rdar://problem/28963058
If we won't show the diagnostics anyway, don't go to the trouble of
performing the typo-corrections, which can be expensive.  This is really
helpful if there is a module import failure, which may cause many names
to fail to resolve and would otherwise trigger typo-correction.

rdar://problem/29003372
@benlangmuir benlangmuir added this to the Swift 3.0 milestone Nov 11, 2016
@benlangmuir
Copy link
Contributor Author

@swift-ci please test

@tkremenek tkremenek merged commit 6ea1f16 into swiftlang:swift-3.0-branch Nov 11, 2016
@benlangmuir benlangmuir deleted the disable-typo-correction-indexing-fatal branch November 11, 2016 17:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants