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
22 lines
337 B
Kotlin
Vendored
22 lines
337 B
Kotlin
Vendored
// FIR_IDENTICAL
|
|
|
|
// MUTE_SIGNATURE_COMPARISON_K2: JS_IR
|
|
// MUTE_SIGNATURE_COMPARISON_K2: NATIVE
|
|
// ^ KT-57818
|
|
|
|
fun foo(): String = ""
|
|
val x = 42
|
|
|
|
val test1 = ""
|
|
val test2 = "abc"
|
|
val test3 = """"""
|
|
val test4 = """abc"""
|
|
val test5 = """
|
|
abc
|
|
"""
|
|
val test6 = "$test1 ${foo()}"
|
|
|
|
val test7 = "$test1"
|
|
val test8 = "${foo()}"
|
|
val test9 = "$x"
|