Skip to content

[4.0] Diagnostics for Minimal and Complete Patterns #9151

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

Closed
wants to merge 3 commits into from

Conversation

CodaFi
Copy link
Contributor

@CodaFi CodaFi commented May 1, 2017

Redoes a phase of type checking to validate patterns for minimality and completeness.

Cherry-picked from #8908, #9121, #9155, and #9180.

@CodaFi
Copy link
Contributor Author

CodaFi commented May 1, 2017

@swift-ci please test

@swift-ci
Copy link
Contributor

swift-ci commented May 1, 2017

Build failed
Jenkins build - Swift Test OS X Platform
Git Commit - c0fb43381fac1c40668e06856ce6821db2a79f86
Test requested by - @CodaFi

@swift-ci
Copy link
Contributor

swift-ci commented May 1, 2017

Build failed
Jenkins build - Swift Test Linux Platform
Git Commit - c0fb43381fac1c40668e06856ce6821db2a79f86
Test requested by - @CodaFi

@CodaFi
Copy link
Contributor Author

CodaFi commented May 1, 2017

Wow, this cherry-pick was pretty bad. I'm gonna rebase and try again.

@CodaFi
Copy link
Contributor Author

CodaFi commented May 1, 2017

@swift-ci please test

@swift-ci
Copy link
Contributor

swift-ci commented May 1, 2017

Build failed
Jenkins build - Swift Test OS X Platform
Git Commit - 15beaaf1ce1222a7e66a78d304da41862f5a6712
Test requested by - @CodaFi

@CodaFi
Copy link
Contributor Author

CodaFi commented May 1, 2017

@swift-ci please test

ERROR(non_exhaustive_switch,none,
"%select{switch must be exhaustive, consider adding |do you want to add }0"
"%select{missing cases|a default clause}1"
"%select{:|?}0 %2", (bool, bool, StringRef))
Copy link
Contributor

Choose a reason for hiding this comment

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

Could you drop the last StringRef? we don't need to duplicate the fixit content.

Copy link
Contributor

Choose a reason for hiding this comment

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

Fixing on master first will be awesome. Thank you!

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Ah yeah. That was leftover from when I thought I could combine this fixit with the other one.

Thanks! I'll shoot a quick pull request over and cherry-pick that in here.

@CodaFi CodaFi reopened this May 3, 2017
@CodaFi
Copy link
Contributor Author

CodaFi commented May 3, 2017

Weird: If you force-push at a branch that becomes even with the one you're targeting a pull request at, it closes it.

@CodaFi
Copy link
Contributor Author

CodaFi commented May 3, 2017

@nkcsgexi These commits are going to be auto-merged anyways, right? I don't think this PR is necessary.

@CodaFi CodaFi closed this May 3, 2017
@CodaFi CodaFi deleted the blastoff branch May 3, 2017 00:41
@nkcsgexi
Copy link
Contributor

nkcsgexi commented May 4, 2017

@CodaFi it seems they won't be auto-merged to swift-4.0-branch, shall we revive the pull request?

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