Skip to content

[4.0] [Parse] Don't tell CodeCompletion nonsense about protocol/AT where clauses #9710

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 2 commits into from
May 17, 2017

Conversation

huonw
Copy link
Contributor

@huonw huonw commented May 17, 2017

Explanation: cherry pick of #9419 . This was misusing an API in a cargo-culted attempt to get better completions for things like protocol Foo where Se<esc>, which just resulted in crashes. The default completions aren't as helpful as they could be, but are definitely better than just crashing.
Scope: Anyone using the new where clauses in Xcode.
Radar: rdar://problem/32256159
Risk: Low: this is removing an incorrectly called, optional function call.
Testing: Swift CI.

huonw added 2 commits May 17, 2017 13:32
…auses.

This doesn't give particularly useful information yet (i.e. Self isn't
listed, see rdar://problem/31981641 ), but it does stop the completion
code from just directly crashing.

Fixes rdar://problem/31981486.
@huonw
Copy link
Contributor Author

huonw commented May 17, 2017

@swift-ci Please test

@slavapestov
Copy link
Contributor

LGTM!

@huonw huonw added this to the Swift 4.0 milestone May 17, 2017
@huonw huonw assigned huonw and ematejska and unassigned huonw May 17, 2017
@huonw huonw merged commit a4e3274 into swiftlang:swift-4.0-branch May 17, 2017
@huonw huonw deleted the where-completion-crash branch May 17, 2017 23:05
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