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
435 B
Kotlin
Vendored
36 lines
435 B
Kotlin
Vendored
// WITH_STDLIB
|
|
// TARGET_BACKEND: JVM
|
|
// SKIP_KT_DUMP
|
|
|
|
// MUTE_SIGNATURE_COMPARISON_K2: ANY
|
|
// ^ KT-57433
|
|
|
|
// FILE: box.kt
|
|
|
|
package k
|
|
|
|
import J
|
|
|
|
var p1 by J()::foo
|
|
var p2 by J()::foo
|
|
|
|
fun box(): String {
|
|
p1 = "O"
|
|
p2 = "K"
|
|
return p1 + p2
|
|
}
|
|
|
|
// FILE: J.java
|
|
|
|
public class J {
|
|
private String s = "Fail";
|
|
|
|
public void setFoo(String s) {
|
|
this.s = s;
|
|
}
|
|
|
|
public String getFoo() {
|
|
return s;
|
|
}
|
|
}
|