[test] Mark tests that use experimental/upcoming features as such

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.
This commit is contained in:
Daniel Rodríguez Troitiño
2024-09-25 23:08:59 -07:00
parent facdb57f39
commit ba68faaed5
727 changed files with 1047 additions and 297 deletions

View File

@@ -1,7 +1,8 @@
// RUN: %target-swift-emit-silgen -target %target-swift-5.1-abi-triple -disable-experimental-parser-round-trip -parse-stdlib -module-name keypaths %s | %FileCheck %s
// FIXME: Remove '-disable-experimental-parser-round-trip'.
// REQUIRES: asserts
// REQUIRES: swift_feature_KeyPathWithStaticMembers
import Swift