[IR] Dump IdSignatures and mangled names in irText tests

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
This commit is contained in:
Sergej Jaskiewicz
2023-04-06 15:07:36 +02:00
committed by Space Team
parent bccf69910d
commit 6e8283a6fe
791 changed files with 36162 additions and 357 deletions
@@ -0,0 +1,22 @@
// CHECK JVM_IR:
// Mangled name: #convert@kotlin.Number(){0§<kotlin.Number>}0:0
// Public signature: /convert|-8929373318028206908[0]
// CHECK JS_IR NATIVE:
// Mangled name: #convert@kotlin.Number(){0§<kotlin.Number>}
// Public signature: /convert|1202542150258287198[0]
fun <R : Number> Number.convert(): R
// CHECK:
// Mangled name: #foo(kotlin.Number){}
// Public signature: /foo|97687418835402471[0]
fun foo(arg: Number): Unit
// CHECK JVM_IR:
// Mangled name computed from Ir: #main(kotlin.Array<kotlin.String>){}
// Mangled name computed from Descriptor: #main(kotlin.Array<kotlin.String>){}%argumentMappedWithError.kt
// Public signature: /main|5561668743171252170[0]
// CHECK JS_IR NATIVE:
// Mangled name: #main(kotlin.Array<kotlin.String>){}
// Public signature: /main|5976701115139892152[0]
fun main(args: Array<String>): Unit