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
852 B
Kotlin
Vendored
36 lines
852 B
Kotlin
Vendored
// CHECK:
|
|
// Mangled name: I1
|
|
// Public signature: /I1|null[0]
|
|
interface I1 {
|
|
|
|
}
|
|
|
|
// CHECK:
|
|
// Mangled name: I2
|
|
// Public signature: /I2|null[0]
|
|
interface I2 {
|
|
|
|
}
|
|
|
|
// CHECK JVM_IR:
|
|
// Mangled name: #component1@I1(){}kotlin.Int
|
|
// Public signature: /component1|8801376328143328436[0]
|
|
// CHECK JS_IR NATIVE:
|
|
// Mangled name: #component1@I1(){}
|
|
// Public signature: /component1|-7381230852082083752[0]
|
|
operator fun I1.component1(): Int
|
|
|
|
// CHECK JVM_IR:
|
|
// Mangled name: #component2@I2(){}kotlin.String
|
|
// Public signature: /component2|-3393912940495634771[0]
|
|
// CHECK JS_IR NATIVE:
|
|
// Mangled name: #component2@I2(){}
|
|
// Public signature: /component2|-7506551577483428650[0]
|
|
operator fun I2.component2(): String
|
|
|
|
// CHECK:
|
|
// Mangled name: #test(I1){}
|
|
// Public signature: /test|-2567635956051433615[0]
|
|
fun test(x: I1): Unit
|
|
|