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
36 lines
920 B
Kotlin
Vendored
36 lines
920 B
Kotlin
Vendored
// CHECK:
|
|
// Mangled name: IC1
|
|
// Public signature: /IC1|null[0]
|
|
interface IC1 {
|
|
|
|
// CHECK JVM_IR:
|
|
// Mangled name: IC1#component1(){}kotlin.Int
|
|
// Public signature: /IC1.component1|-8217597213800111288[0]
|
|
// CHECK JS_IR NATIVE:
|
|
// Mangled name: IC1#component1(){}
|
|
// Public signature: /IC1.component1|162597135895221648[0]
|
|
abstract operator fun component1(): Int
|
|
|
|
}
|
|
|
|
// CHECK:
|
|
// Mangled name: IC2
|
|
// Public signature: /IC2|null[0]
|
|
interface IC2 {
|
|
|
|
// CHECK JVM_IR:
|
|
// Mangled name: IC2#component2(){}kotlin.String
|
|
// Public signature: /IC2.component2|1228864375093914597[0]
|
|
// CHECK JS_IR NATIVE:
|
|
// Mangled name: IC2#component2(){}
|
|
// Public signature: /IC2.component2|3796717572321500973[0]
|
|
abstract operator fun component2(): String
|
|
|
|
}
|
|
|
|
// CHECK:
|
|
// Mangled name: #test(kotlin.Any){}
|
|
// Public signature: /test|-7985792749252989017[0]
|
|
fun test(x: Any): Unit
|
|
|