mirror of
https://github.com/apple/swift.git
synced 2025-12-21 12:14:44 +01:00
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.
35 lines
1.1 KiB
Swift
35 lines
1.1 KiB
Swift
// RUN: %target-swift-frontend %s -emit-sil -o /dev/null -verify
|
|
// RUN: %target-swift-frontend %s -emit-sil -o /dev/null -verify -strict-concurrency=targeted
|
|
// RUN: %target-swift-frontend %s -emit-sil -o /dev/null -verify -strict-concurrency=complete
|
|
// RUN: %target-swift-frontend %s -emit-sil -o /dev/null -verify -strict-concurrency=complete -enable-upcoming-feature RegionBasedIsolation
|
|
|
|
// REQUIRES: concurrency
|
|
// REQUIRES: swift_feature_RegionBasedIsolation
|
|
|
|
public protocol P {
|
|
associatedtype T
|
|
@MainActor func f(_: T)
|
|
@MainActor func g(_: T)
|
|
}
|
|
public struct S : P {
|
|
public func g(_: Int) {}
|
|
public func f(_: T) {}
|
|
}
|
|
|
|
// https://github.com/apple/swift/issues/61602
|
|
@available(SwiftStdlib 5.1, *)
|
|
@MainActor protocol ProtocolWithAssociatedTypes {
|
|
associatedtype ID: Hashable
|
|
associatedtype Value
|
|
|
|
subscript(_ id: ID) -> Value { get set }
|
|
}
|
|
|
|
@available(SwiftStdlib 5.1, *)
|
|
final class ClassConforming<ID: Hashable,Value>: ProtocolWithAssociatedTypes {
|
|
subscript(id: ID) -> Value {
|
|
get { fatalError() }
|
|
set { fatalError() }
|
|
}
|
|
}
|