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
44 lines
1.1 KiB
Kotlin
Vendored
44 lines
1.1 KiB
Kotlin
Vendored
// CHECK:
|
|
// Mangled name: A
|
|
// Public signature: /A|null[0]
|
|
object A {
|
|
// CHECK:
|
|
// Mangled name: A#<init>(){}
|
|
// Public signature: /A.<init>|-5645683436151566731[0]
|
|
private constructor() /* primary */
|
|
|
|
}
|
|
|
|
// CHECK:
|
|
// Mangled name: B
|
|
// Public signature: /B|null[0]
|
|
object B {
|
|
// CHECK:
|
|
// Mangled name: B#<init>(){}
|
|
// Public signature: /B.<init>|-5645683436151566731[0]
|
|
private constructor() /* primary */
|
|
|
|
// CHECK JVM_IR:
|
|
// Mangled name: B#component1@A(){}kotlin.Int
|
|
// Public signature: /B.component1|-7852292492190161170[0]
|
|
// CHECK JS_IR NATIVE:
|
|
// Mangled name: B#component1@A(){}
|
|
// Public signature: /B.component1|-5209316971718544805[0]
|
|
operator fun A.component1(): Int
|
|
|
|
// CHECK JVM_IR:
|
|
// Mangled name: B#component2@A(){}kotlin.Int
|
|
// Public signature: /B.component2|-9145888741821901515[0]
|
|
// CHECK JS_IR NATIVE:
|
|
// Mangled name: B#component2@A(){}
|
|
// Public signature: /B.component2|-4967140045736561606[0]
|
|
operator fun A.component2(): Int
|
|
|
|
}
|
|
|
|
// CHECK:
|
|
// Mangled name: #test@B(){}
|
|
// Public signature: /test|5810566108753944346[0]
|
|
fun B.test(): Unit
|
|
|