duplicates:

• SR-483 Exhaustivity checking for switch statement with wildcards doesn't work properly

Issue Description:

Bit of a weird issue, let's say we have a two-case enum called Result.

enum Result {
    case Success, Failure
}

And then I have a tuple of two Results. If I switch on the tuple using the following cases, the Swift compiler gives me an error that the switch is not exhaustive.

switch tuple {
case (.Success, .Success): ...
case (_, .Error): ...
case (.Error, _): ...
}

In this simple example it doesn't really matter because I could use a default case, but often I'll have an ErrorType instance associated with the Error case, and I need either one or the other extracted using the case statements. I've solved this in my own code by just using an exhaustive, explicit switch, but as mentioned on Twitter ( https://twitter.com/jckarter/status/724665175018606592 ) this is a bug, as Swift should be able to infer the exhaustiveness.