[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,30 @@
// CHECK:
// Mangled name: IFoo
// Public signature: /IFoo|null[0]
fun interface IFoo {
// CHECK:
// Mangled name: IFoo#foo(kotlin.Int){}
// Public signature: /IFoo.foo|-104159190164110731[0]
abstract fun foo(i: Int): Unit
}
// CHECK:
// Mangled name: #test(){}
// Public signature: /test|6620506149988718649[0]
fun test(): Unit
// CHECK:
// Mangled name: #useFoo(IFoo){}
// Public signature: /useFoo|-5008863146598304258[0]
fun useFoo(foo: IFoo): Unit
// CHECK JVM_IR:
// Mangled name: #withVararg(kotlin.IntArray...){}kotlin.Int
// Public signature: /withVararg|2262699225692856772[0]
// CHECK JS_IR NATIVE:
// Mangled name: #withVararg(kotlin.IntArray...){}
// Public signature: /withVararg|2511032413940817176[0]
fun withVararg(vararg xs: Int): Int