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
813 B
Kotlin
Vendored
25 lines
813 B
Kotlin
Vendored
// CHECK JVM_IR:
|
|
// Mangled name: #create(){}kotlin.String
|
|
// Public signature: /create|-1557561735696060682[0]
|
|
// CHECK JS_IR NATIVE:
|
|
// Mangled name: #create(){}
|
|
// Public signature: /create|9033430362705119523[0]
|
|
fun create(): String
|
|
|
|
// CHECK JVM_IR:
|
|
// Mangled name: #create(kotlin.Boolean){}kotlin.String
|
|
// Public signature: /create|-3400482347981983007[0]
|
|
// CHECK JS_IR NATIVE:
|
|
// Mangled name: #create(kotlin.Boolean){}
|
|
// Public signature: /create|-2263398152642299020[0]
|
|
fun create(b: Boolean): String
|
|
|
|
// CHECK JVM_IR:
|
|
// Mangled name: #create(kotlin.String){}kotlin.String
|
|
// Public signature: /create|-6120250208000719461[0]
|
|
// CHECK JS_IR NATIVE:
|
|
// Mangled name: #create(kotlin.String){}
|
|
// Public signature: /create|-5890518877103900297[0]
|
|
fun create(s: String): String
|
|
|