6 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
Erik Eckstein	6e61c202a7	embedded: fix a typo in an error message	2024-09-25 19:32:15 +02:00
Erik Eckstein	ba9bfaf5d5	VTableSpecializer: fix a crash for methods which have their own generic parameters ... rdar://133334324	2024-08-21 17:01:35 +02:00
Kuba Mracek	f1aba675ef	[embedded] Mark all embedded tests as REQUIRES: swift_in_compiler	2023-11-07 10:01:03 -08:00
zoecarver	8afe689194	[embedded] Add -wmo to a number of tests after rebase.	2023-09-15 16:50:29 -06:00
Kuba Mracek	e2de477609	[embedded] avoid metadata accessors, fix vtable map, add a diagnostic on non-final generic functions	2023-09-12 16:57:09 -07:00