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
29 lines
631 B
Kotlin
Vendored
29 lines
631 B
Kotlin
Vendored
// WITH_STDLIB
|
|
|
|
// MUTE_SIGNATURE_COMPARISON_K2: JS_IR
|
|
// MUTE_SIGNATURE_COMPARISON_K2: NATIVE
|
|
// ^ KT-57818
|
|
|
|
fun interface Fn<T, R> {
|
|
fun run(s: String, i: Int, t: T): R
|
|
}
|
|
|
|
class J {
|
|
fun runConversion(f1: Fn<String, Int>, f2: Fn<Int, String>): Int {
|
|
return f1.run("Bar", 1, f2.run("Foo", 42, 239))
|
|
}
|
|
}
|
|
|
|
val fsi = object : Fn<String, Int> {
|
|
override fun run(s: String, i: Int, t: String): Int = 1
|
|
}
|
|
|
|
val fis = object : Fn<Int, String> {
|
|
override fun run(s: String, i: Int, t: Int): String = ""
|
|
}
|
|
|
|
fun test(j: J) {
|
|
j.runConversion(fsi) { s, i, ti -> ""}
|
|
j.runConversion({ s, i, ts -> 1 }, fis)
|
|
}
|