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
10 lines
341 B
Kotlin
Vendored
10 lines
341 B
Kotlin
Vendored
// CHECK JVM_IR:
|
|
// Mangled name computed from Ir: #main(){}
|
|
// Mangled name computed from Descriptor: #main(){}%suspendConversionForExtensionFunction.kt
|
|
// Public signature: /main|8952895695315889943[0]
|
|
// CHECK JS_IR NATIVE:
|
|
// Mangled name: #main(){}
|
|
// Public signature: /main|-4284757841571462650[0]
|
|
fun main(): Unit
|
|
|