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
24 lines
790 B
Kotlin
Vendored
24 lines
790 B
Kotlin
Vendored
// CHECK JVM_IR:
|
|
// Mangled name: #test(kotlin.Int){}kotlin.Int
|
|
// Public signature: /test|-291422697420002546[0]
|
|
// CHECK JS_IR NATIVE:
|
|
// Mangled name: #test(kotlin.Int){}
|
|
// Public signature: /test|7577436859890467564[0]
|
|
fun test(i: Int): Int
|
|
|
|
// CHECK:
|
|
// Mangled name: #testEmptyBranches1(kotlin.Boolean){}
|
|
// Public signature: /testEmptyBranches1|6749407893686345218[0]
|
|
fun testEmptyBranches1(flag: Boolean): Unit
|
|
|
|
// CHECK:
|
|
// Mangled name: #testEmptyBranches2(kotlin.Boolean){}
|
|
// Public signature: /testEmptyBranches2|3860029463289034948[0]
|
|
fun testEmptyBranches2(flag: Boolean): Unit
|
|
|
|
// CHECK:
|
|
// Mangled name: #testEmptyBranches3(kotlin.Boolean){}
|
|
// Public signature: /testEmptyBranches3|-3957627705861131354[0]
|
|
fun testEmptyBranches3(flag: Boolean): Unit
|
|
|