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
19 lines
338 B
Kotlin
Vendored
19 lines
338 B
Kotlin
Vendored
// TARGET_BACKEND: JVM
|
|
// FIR_IDENTICAL
|
|
// WITH_STDLIB
|
|
// SKIP_KT_DUMP
|
|
|
|
// MUTE_SIGNATURE_COMPARISON_K2: ANY
|
|
// ^ KT-57429
|
|
|
|
// FILE: kt44993.kt
|
|
fun f(r: KotlinBox<JavaBox>): String =
|
|
r?.data?.element!!
|
|
|
|
class KotlinBox<T>(@JvmField val data: T?)
|
|
|
|
// FILE: JavaBox.java
|
|
public class JavaBox {
|
|
public final String element = "OK";
|
|
}
|