Skip to content

Disable typo-correction by default until we can make it work within acceptable performance bounds #25674

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
Jun 25, 2019

Conversation

akyrtzi
Copy link
Contributor

@akyrtzi akyrtzi commented Jun 22, 2019

Typo-correction can be so expensive that it can slow down typechecking over 10x.
It can be a significant productivity drain for developing on large projects.

Unfortunately it is best that we disable it until we can dedicate the time to address its performance issues
and we are certain it works within acceptable performance bounds.

rdar://51966070

@akyrtzi akyrtzi requested a review from rjmccall June 22, 2019 01:18
…cceptable performance bounds

Typo-correction can be so expensive that it can slow down typechecking over 10x.
It can be a significant productivity drain for developing on large projects.

Unfortunately it is best that we disable it until we can dedicate the time to address its performance issues
and we are certain it works within acceptable performance bounds.

rdar://51966070
@akyrtzi akyrtzi force-pushed the disable-typo-correction branch from 33959df to cf65b8f Compare June 23, 2019 00:02
@akyrtzi
Copy link
Contributor Author

akyrtzi commented Jun 23, 2019

@swift-ci smoke test

@akyrtzi akyrtzi requested a review from DougGregor June 25, 2019 01:41
Copy link
Contributor

@rjmccall rjmccall left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay

Copy link
Member

@DougGregor DougGregor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Depressing, but okay.

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.

3 participants