Commit Graph

8 Commits

Author SHA1 Message Date
Daniel Rodríguez Troitiño
ba68faaed5 [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.
2024-11-02 11:46:46 -07:00
Kuba Mracek
ff1f8adac8 [embedded] Implement non-allocating embedded Swift mode, under -no-allocations flag 2023-12-11 09:00:50 -08:00
Kuba Mracek
f1aba675ef [embedded] Mark all embedded tests as REQUIRES: swift_in_compiler 2023-11-07 10:01:03 -08:00
Kuba Mracek
30046b1f8d [embedded] Update wording on existential diagnostics, take 2 2023-10-14 14:03:59 -07:00
Kuba Mracek
bbe111cca6 [embedded] Update wording on 'no existentials' diagnostic 2023-10-13 10:31:14 -07:00
Kuba Mracek
d5b1abb726 [embedded] Improve the diagnostic message when using an existential 2023-10-09 16:20:08 -07:00
zoecarver
8afe689194 [embedded] Add -wmo to a number of tests after rebase. 2023-09-15 16:50:29 -06:00
Kuba Mracek
ae0ec1ca5e [embedded] Fix compiler crash in getRuntimeEffect when processing ExistentialMetatypeInst 2023-09-13 15:06:17 -07:00