Sergej Jaskiewicz
6e8283a6fe
The reason #1 for this feature is that we want to test IdSignatures generated for declarations. Currently, there is no (easy) way to ensure that a change in the signature building logic doesn't cause any breaking changes wrt klibs. Now, most IdSignatures include hashed mangled names in them, so even if we catch a regression where the included hash changes, there would be no way of knowing immediately what caused it, unless we'd also have mangled names in the expectations. The reason #2 is to test the manglers themselves. Currently, there are no tests for them. They heavily duplicate each other, this is already causing issues (see KT-57427) that would be very hard to catch without these tests. ^KT-58238 Fixed
29 lines
643 B
Kotlin
Vendored
29 lines
643 B
Kotlin
Vendored
// SKIP_SIGNATURE_DUMP
|
|
// ^ KT-57429, different types in annotations generated by K1 and K2
|
|
|
|
package ann
|
|
|
|
annotation class Test1<T>(val x: Int)
|
|
|
|
annotation class Test2<T1 : Any, T2>(val x: Int = 0)
|
|
|
|
interface I<T>
|
|
|
|
annotation class Test3<T1, T2 : I<T1>>(val x: Test1<I<T2>>)
|
|
|
|
class C<T> : I<T>
|
|
|
|
annotation class Test4(val x: Array<Test3<Int, C<Int>>>)
|
|
|
|
class ARG
|
|
|
|
annotation class Test5<T>(vararg val xs: Test3<T, C<T>>)
|
|
|
|
|
|
@Test1<ARG>(42)
|
|
@Test2<String, String>(38)
|
|
@Test3<String, C<String>>(Test1(39))
|
|
@Test4([Test3(Test1(40)), Test3(Test1(50)), Test3(Test1(60))])
|
|
@Test5<ARG>(*arrayOf(Test3(Test1(70))), *arrayOf(Test3(Test1(80))))
|
|
class CC
|