mirror of
https://github.com/apple/swift.git
synced 2025-12-21 12:14:44 +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
520 B
Swift
13 lines
520 B
Swift
// RUN: %empty-directory(%t)
|
|
|
|
// RUN: %target-swift-frontend -swift-version 5 -enable-library-evolution -module-name unsafe -emit-module -o %t/unsafe.swiftmodule -emit-module-interface-path - %s -enable-experimental-feature AllowUnsafeAttribute | %FileCheck %s
|
|
|
|
// REQUIRES: swift_feature_AllowUnsafeAttribute
|
|
|
|
// CHECK: #if compiler(>=5.3) && $AllowUnsafeAttribute
|
|
// CHECK: @unsafe public func testFunction()
|
|
// CHECK: #else
|
|
// CHECK: public func testFunction()
|
|
// CHECK: #endif
|
|
@unsafe public func testFunction() { }
|