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
9 lines
464 B
Kotlin
Vendored
9 lines
464 B
Kotlin
Vendored
// CHECK JVM_IR:
|
|
// Mangled name: #test(kotlin.Any?;kotlin.Function3<kotlin.Any,kotlin.Int,kotlin.String,kotlin.Unit>){}kotlin.Unit?
|
|
// Public signature: /test|-6483776340446886488[0]
|
|
// CHECK JS_IR NATIVE:
|
|
// Mangled name: #test(kotlin.Any?;kotlin.Function3<kotlin.Any,kotlin.Int,kotlin.String,kotlin.Unit>){}
|
|
// Public signature: /test|7562359801694057104[0]
|
|
fun test(receiver: Any?, fn: @ExtensionFunctionType Function3<Any, Int, String, Unit>): Unit?
|
|
|