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
789 B
Kotlin
Vendored
25 lines
789 B
Kotlin
Vendored
// CHECK JVM_IR:
|
|
// Mangled name: #box(){}kotlin.String
|
|
// Public signature: /box|-9347091776561469[0]
|
|
// CHECK JS_IR NATIVE:
|
|
// Mangled name: #box(){}
|
|
// Public signature: /box|2173511048851971368[0]
|
|
fun box(): String
|
|
|
|
// CHECK JVM_IR:
|
|
// Mangled name: #test_1(kotlin.Any?){}kotlin.String?
|
|
// Public signature: /test_1|8306101080862525041[0]
|
|
// CHECK JS_IR NATIVE:
|
|
// Mangled name: #test_1(kotlin.Any?){}
|
|
// Public signature: /test_1|6244764910155513609[0]
|
|
fun test_1(value: Any?): String?
|
|
|
|
// CHECK JVM_IR:
|
|
// Mangled name: #test_2(kotlin.Any?){}kotlin.String?
|
|
// Public signature: /test_2|4804906371697221872[0]
|
|
// CHECK JS_IR NATIVE:
|
|
// Mangled name: #test_2(kotlin.Any?){}
|
|
// Public signature: /test_2|-2820233899677445404[0]
|
|
fun test_2(value: Any?): String?
|
|
|