mirror of
https://github.com/apple/swift.git
synced 2025-12-21 12:14:44 +01:00
c3ce40ddb6
Currently all `ComponentSteps` created by `DependentComponentSplitterStep` share the same `Solutions` vector. Because of this, the `ComponentStep`s might modify solutions created by previous `ComponentStep`s. Use different `Solutions` vectors for each `ComponentStep` to avoid sharing information between the `ComponentStep`s. The concrete manifestation in the added test case is that the `Bar` overload gets added to `Solutions`, it’s score gets reduced by its `ComponentStep` original score, then the `Foo` overload gets added to `Solutions` and both solutions have their score decreased by the `OriginalScore` of `Foo`’s `ComponentStep`, causing `Bar`’s score to underflow. Fixes rdar://78780840 [SR-14692]
28 lines
868 B
Swift
28 lines
868 B
Swift
// RUN: %target-typecheck-verify-swift
|
|
|
|
enum Foo { case foo }
|
|
enum Bar { case bar }
|
|
|
|
@resultBuilder struct ViewBuilder2 {
|
|
static func buildBlock(_ content: MyView) -> MyView { fatalError() }
|
|
static func buildIf(_ content: MyView?) -> MyView { fatalError() }
|
|
}
|
|
|
|
func makeView(@ViewBuilder2 content: () -> MyView) { fatalError() }
|
|
|
|
struct MyView {
|
|
init() { fatalError() }
|
|
|
|
func qadding(bar: Foo) -> MyView { fatalError() } // expected-note{{incorrect labels for candidate (have: '(_:)', expected: '(bar:)')}}
|
|
func qadding(foo: Foo) -> MyView { fatalError() } // expected-note{{incorrect labels for candidate (have: '(_:)', expected: '(foo:)')}}
|
|
}
|
|
|
|
func testCase() {
|
|
let array: [Int]? = []
|
|
|
|
makeView() {
|
|
if array?.isEmpty == false {
|
|
MyView().qadding(.foo) // expected-error{{no exact matches in call to instance method 'qadding'}}
|
|
}
|
|
}
|
|
} |