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
23 lines
353 B
Kotlin
Vendored
23 lines
353 B
Kotlin
Vendored
// FIR_IDENTICAL
|
|
|
|
// MUTE_SIGNATURE_COMPARISON_K2: JS_IR
|
|
// MUTE_SIGNATURE_COMPARISON_K2: NATIVE
|
|
// ^ KT-57818
|
|
|
|
import A.foo
|
|
import A.bar
|
|
import A.fooExt
|
|
import A.barExt
|
|
|
|
object A {
|
|
fun foo() = 1
|
|
fun Int.fooExt() = 2
|
|
val bar = 42
|
|
val Int.barExt get() = 43
|
|
}
|
|
|
|
val test1 = foo()
|
|
val test2 = bar
|
|
val test3 = 1.fooExt()
|
|
val test4 = 1.barExt
|