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
25 lines
902 B
Kotlin
Vendored
25 lines
902 B
Kotlin
Vendored
// CHECK JVM_IR:
|
|
// Mangled name: #test1(kotlin.Int;kotlin.Int){}kotlin.Boolean
|
|
// Public signature: /test1|-7551143999400464285[0]
|
|
// CHECK JS_IR NATIVE:
|
|
// Mangled name: #test1(kotlin.Int;kotlin.Int){}
|
|
// Public signature: /test1|-6134767217751638375[0]
|
|
fun test1(a: Int, b: Int): Boolean
|
|
|
|
// CHECK JVM_IR:
|
|
// Mangled name: #test2(kotlin.Int;kotlin.Int){}kotlin.Boolean
|
|
// Public signature: /test2|29360423018429037[0]
|
|
// CHECK JS_IR NATIVE:
|
|
// Mangled name: #test2(kotlin.Int;kotlin.Int){}
|
|
// Public signature: /test2|-1200247296907510564[0]
|
|
fun test2(a: Int, b: Int): Boolean
|
|
|
|
// CHECK JVM_IR:
|
|
// Mangled name: #test3(kotlin.Any?;kotlin.Any?){}kotlin.Boolean
|
|
// Public signature: /test3|-3154163417477574713[0]
|
|
// CHECK JS_IR NATIVE:
|
|
// Mangled name: #test3(kotlin.Any?;kotlin.Any?){}
|
|
// Public signature: /test3|6801898630268838874[0]
|
|
fun test3(a: Any?, b: Any?): Boolean
|
|
|