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
26 lines
643 B
Kotlin
Vendored
26 lines
643 B
Kotlin
Vendored
// CHECK:
|
|
// Mangled name: Test
|
|
// Public signature: /Test|null[0]
|
|
class Test<T : Any?> : J<T> {
|
|
// CHECK:
|
|
// Mangled name: Test{}x
|
|
// Public signature: /Test.x|-8060530855978347579[0]
|
|
val x: T
|
|
// CHECK JVM_IR:
|
|
// Mangled name: Test#<get-x>(){}1:0
|
|
// Public signature: /Test.x.<get-x>|-8893883356128097563[0]
|
|
get
|
|
|
|
// CHECK:
|
|
// Mangled name: Test#<init>(1:0){}
|
|
// Public signature: /Test.<init>|-8731461708390519279[0]
|
|
constructor(x: T) /* primary */
|
|
|
|
// CHECK:
|
|
// Mangled name: Test#test(J.B<1:0>){}
|
|
// Public signature: /Test.test|7386642793853999047[0]
|
|
fun test(b: B<T>): Unit
|
|
|
|
}
|
|
|