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.
38 lines
833 B
Swift
38 lines
833 B
Swift
// RUN: %target-run-simple-swift(-swift-version 5 -enable-experimental-feature Embedded -parse-as-library -runtime-compatibility-version none -wmo) | %FileCheck %s
|
|
|
|
// REQUIRES: swift_in_compiler
|
|
// REQUIRES: executable_test
|
|
// REQUIRES: optimized_stdlib
|
|
// REQUIRES: OS=macosx || OS=linux-gnu
|
|
// REQUIRES: swift_feature_Embedded
|
|
|
|
struct Event {
|
|
var id: String
|
|
var n: Int
|
|
}
|
|
|
|
extension Event: CustomStringConvertible {
|
|
var description: String {
|
|
return "id: \(id), n: \(n)"
|
|
}
|
|
}
|
|
|
|
@main
|
|
struct Main {
|
|
static func main() {
|
|
var events: [Event] = []
|
|
for i in 0 ..< 5 {
|
|
events.append(Event(id: "event\(i)", n: i))
|
|
}
|
|
for event in events {
|
|
print(event)
|
|
}
|
|
}
|
|
}
|
|
|
|
// CHECK: id: event0, n: 0
|
|
// CHECK: id: event1, n: 1
|
|
// CHECK: id: event2, n: 2
|
|
// CHECK: id: event3, n: 3
|
|
// CHECK: id: event4, n: 4
|