mirror of
https://github.com/apple/swift.git
synced 2025-12-14 20:36:38 +01:00
7a137d6756
Previously we would wait until CSApply, which would trigger their type-checking in `coercePatternToType`. This caused a number of bugs, and hampered solver-based completion, which does not run CSApply. Instead, form a conjunction of all the ExprPatterns present, which preserves some of the previous isolation behavior (though does not provide complete isolation). We can then modify `coercePatternToType` to accept a closure, which allows the solver to take over rewriting the ExprPatterns it has already solved. This then sets the stage for the complete removal of `coercePatternToType`, and doing all pattern type-checking in the solver.
19 lines
443 B
Swift
19 lines
443 B
Swift
// RUN: %target-typecheck-verify-swift -target %target-cpu-apple-macosx10.15 -swift-version 5
|
|
// REQUIRES: objc_interop
|
|
// REQUIRES: OS=macosx
|
|
|
|
import SwiftUI
|
|
|
|
struct ContentView: View {
|
|
@State private var currentPage = "1"
|
|
|
|
var body: some View {
|
|
switch currentPage {
|
|
case 1: // expected-error {{expression pattern of type 'Int' cannot match values of type 'String'}}
|
|
Text("1")
|
|
default:
|
|
Text("default")
|
|
}
|
|
}
|
|
}
|