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
38 lines
482 B
Kotlin
Vendored
38 lines
482 B
Kotlin
Vendored
// TARGET_BACKEND: JS_IR
|
|
|
|
// MUTE_SIGNATURE_COMPARISON_K2: ANY
|
|
// ^ KT-57566
|
|
|
|
val d1: dynamic = 1
|
|
|
|
val p: Int = 1
|
|
|
|
var d2: dynamic = p
|
|
|
|
fun withDynamic(d: dynamic) = d
|
|
|
|
fun test1(s: String) {
|
|
withDynamic(s)
|
|
}
|
|
|
|
fun test2(a: Any) {
|
|
val d: dynamic = a
|
|
}
|
|
|
|
fun test3(a: Any?) {
|
|
val d: dynamic = a
|
|
}
|
|
|
|
fun test4(a: Any, s: String, na: Any?) {
|
|
var d: dynamic = p
|
|
d = a
|
|
d = na
|
|
d = s
|
|
}
|
|
|
|
fun test5(a: Any, s: String, na: Any?) {
|
|
d2 = a
|
|
d2 = na
|
|
d2 = s
|
|
}
|