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
17 lines
530 B
Kotlin
Vendored
17 lines
530 B
Kotlin
Vendored
// CHECK JVM_IR:
|
|
// Mangled name: #test_1(){}kotlin.String
|
|
// Public signature: /test_1|118893848170480080[0]
|
|
// CHECK JS_IR NATIVE:
|
|
// Mangled name: #test_1(){}
|
|
// Public signature: /test_1|9184463131871799545[0]
|
|
fun test_1(): String
|
|
|
|
// CHECK JVM_IR:
|
|
// Mangled name: #test_2(kotlin.Boolean){}kotlin.Boolean
|
|
// Public signature: /test_2|1864697323811942156[0]
|
|
// CHECK JS_IR NATIVE:
|
|
// Mangled name: #test_2(kotlin.Boolean){}
|
|
// Public signature: /test_2|-1271056002368224685[0]
|
|
fun test_2(b: Boolean): Boolean
|
|
|