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
33 lines
794 B
Kotlin
Vendored
33 lines
794 B
Kotlin
Vendored
// CHECK:
|
|
// Mangled name: IA
|
|
// Public signature: /IA|null[0]
|
|
interface IA {
|
|
|
|
// CHECK JVM_IR:
|
|
// Mangled name: IA#get(kotlin.String){}kotlin.Int
|
|
// Public signature: /IA.get|8115151130332405730[0]
|
|
// CHECK JS_IR NATIVE:
|
|
// Mangled name: IA#get(kotlin.String){}
|
|
// Public signature: /IA.get|-2844435113185872994[0]
|
|
abstract operator fun get(index: String): Int
|
|
|
|
}
|
|
|
|
// CHECK:
|
|
// Mangled name: IB
|
|
// Public signature: /IB|null[0]
|
|
interface IB {
|
|
|
|
// CHECK:
|
|
// Mangled name: IB#set@IA(kotlin.String;kotlin.Int){}
|
|
// Public signature: /IB.set|-3878244067281394744[0]
|
|
abstract operator fun IA.set(index: String, value: Int): Unit
|
|
|
|
}
|
|
|
|
// CHECK:
|
|
// Mangled name: #test@IB(IA){}
|
|
// Public signature: /test|-3494937446551267445[0]
|
|
fun IB.test(a: IA): Unit
|
|
|