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.
40 lines
894 B
Swift
40 lines
894 B
Swift
// RUN: %empty-directory(%t)
|
|
// RUN: %target-swift-emit-module-interface(%t.swiftinterface) \
|
|
// RUN: %s \
|
|
// RUN: -enable-experimental-feature CoroutineAccessors \
|
|
// RUN: -module-name Rock
|
|
// RUN: %FileCheck %s < %t.swiftinterface
|
|
// RUN: %target-swift-typecheck-module-from-interface(%t.swiftinterface) -module-name Rock
|
|
|
|
// REQUIRES: swift_feature_CoroutineAccessors
|
|
|
|
var _i: Int = 0
|
|
|
|
// CHECK: #if compiler(>=5.3) && $CoroutineAccessors
|
|
// CHECK-NEXT: public var i: Swift.Int {
|
|
// CHECK-NEXT: _read
|
|
// CHECK-NEXT: read
|
|
// CHECK-NEXT: _modify
|
|
// CHECK-NEXT: modify
|
|
// CHECK-NEXT: }
|
|
// CHECK-NEXT: #else
|
|
// CHECK-NEXT: public var i: Swift.Int {
|
|
// CHECK-NEXT: _read
|
|
// CHECK-NEXT: _modify
|
|
// CHECK-NEXT: }
|
|
// CHECK-NEXT: #endif
|
|
public var i: Int {
|
|
_read {
|
|
yield _i
|
|
}
|
|
read {
|
|
yield _i
|
|
}
|
|
_modify {
|
|
yield &_i
|
|
}
|
|
modify {
|
|
yield &_i
|
|
}
|
|
}
|