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.
13 lines
425 B
Swift
13 lines
425 B
Swift
// RUN: not %target-swift-frontend -typecheck %s 2>&1 | %FileCheck --check-prefix=CHECK-WITHOUT %s
|
|
// RUN: %target-typecheck-verify-swift -enable-experimental-static-assert
|
|
// RUN: %target-typecheck-verify-swift -enable-experimental-feature StaticAssert
|
|
|
|
// REQUIRES: swift_feature_StaticAssert
|
|
|
|
#if compiler(>=5.3) && $StaticAssert
|
|
#assert(true)
|
|
#else
|
|
// CHECK-WITHOUT: cannot find 'complete' in scope
|
|
complete junk
|
|
#endif
|