mirror of
https://github.com/apple/swift.git
synced 2025-12-14 20:36:38 +01:00
ba68faaed5
Find all the usages of `--enable-experimental-feature` or `--enable-upcoming-feature` in the tests and replace some of the `REQUIRES: asserts` to use `REQUIRES: swift-feature-Foo` instead, which should correctly apply to depending on the asserts/noasserts mode of the toolchain for each feature. Remove some comments that talked about enabling asserts since they don't apply anymore (but I might had miss some). All this was done with an automated script, so some formatting weirdness might happen, but I hope I fixed most of those. There might be some tests that were `REQUIRES: asserts` that might run in `noasserts` toolchains now. This will normally be because their feature went from experimental to upcoming/base and the tests were not updated.
22 lines
874 B
Swift
22 lines
874 B
Swift
// RUN: %target-swift-frontend -o /dev/null -emit-sil %s -verify
|
|
// RUN: %target-swift-frontend -o /dev/null -emit-sil %s -verify -strict-concurrency=targeted
|
|
// RUN: %target-swift-frontend -o /dev/null -emit-sil %s -verify -strict-concurrency=complete
|
|
// RUN: %target-swift-frontend -o /dev/null -emit-sil %s -verify -strict-concurrency=complete -enable-upcoming-feature RegionBasedIsolation
|
|
|
|
// REQUIRES: swift_feature_RegionBasedIsolation
|
|
|
|
// This triggers a conformance check with SuppressDiagnostics=true.
|
|
let x = S().f {}
|
|
|
|
protocol P {
|
|
associatedtype A
|
|
|
|
func f(_: A) -> Int // expected-note {{expected sendability to match requirement here}}
|
|
}
|
|
|
|
struct S : P {
|
|
typealias A = () -> ()
|
|
func f(_: @Sendable () -> ()) -> Int { return 0 }
|
|
// expected-warning@-1 {{sendability of function types in instance method 'f' does not match requirement in protocol 'P'}}
|
|
}
|