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.
20 lines
653 B
Swift
20 lines
653 B
Swift
// RUN: %target-swift-frontend -emit-sil -disable-experimental-parser-round-trip -disable-availability-checking -enable-experimental-feature ValueGenerics -enable-experimental-feature BuiltinModule %s
|
|
|
|
// REQUIRES: swift_feature_BuiltinModule
|
|
// REQUIRES: swift_feature_ValueGenerics
|
|
|
|
import Builtin
|
|
|
|
struct MyVector<let N: Int, T: ~Copyable>: ~Copyable {
|
|
var storage: Builtin.FixedArray<N, T>
|
|
|
|
init() {
|
|
// make sure that `Builtin.emplace` considers the result storage
|
|
// initialized, even if the closure doesn't actually do anything
|
|
// with the pointer
|
|
self.storage = Builtin.emplace { ptr in
|
|
}
|
|
}
|
|
}
|
|
|