Files
swift-mirror/test/Interpreter/value_generics.swift
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

40 lines
932 B
Swift

// RUN: %target-run-simple-swift(-enable-experimental-feature ValueGenerics -Xfrontend -disable-availability-checking -Xfrontend -disable-experimental-parser-round-trip) | %FileCheck %s
// UNSUPPORTED: use_os_stdlib
// UNSUPPORTED: back_deployment_runtime
// REQUIRES: executable_test
// REQUIRES: swift_feature_ValueGenerics
struct A<let N: Int, let M: Int> {}
extension A where N == 2 {
struct B {}
}
extension A where M == 5 {
struct C {}
}
extension A where N == M {
struct D {}
}
func getA<let N: Int>() -> A<N, N> {
A()
}
// CHECK: main.A<123, 321>
print(_typeName(A<123, 321>.self, qualified: true))
// CHECK: (extension in main):main.A<2, 9582>.B
print(_typeName(A<2, 9582>.B.self, qualified: true))
// CHECK: (extension in main):main.A<942735, 5>.C
print(_typeName(A<942735, 5>.C.self, qualified: true))
let x: A<-5, -5> = getA()
// CHECK: main.A<-5, -5>
print(_typeName(type(of: x), qualified: true))