[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,36 @@
// CHECK:
// Mangled name: Foo
// Public signature: /Foo|null[0]
fun interface Foo {
// CHECK JVM_IR:
// Mangled name: Foo#invoke(){}kotlin.String
// Public signature: /Foo.invoke|8861605044563078664[0]
// CHECK JS_IR NATIVE:
// Mangled name: Foo#invoke(){}
// Public signature: /Foo.invoke|-4663091332620260873[0]
abstract fun invoke(): String
}
// CHECK JVM_IR:
// Mangled name: #foo(Foo){}kotlin.String
// Public signature: /foo|-5888774885663875480[0]
// CHECK JS_IR NATIVE:
// Mangled name: #foo(Foo){}
// Public signature: /foo|-8233162121880232317[0]
fun foo(f: Foo): String
// CHECK JVM_IR:
// Mangled name: #test(){}kotlin.String
// Public signature: /test|-7008832412320199001[0]
// CHECK JS_IR NATIVE:
// Mangled name: #test(){}
// Public signature: /test|6620506149988718649[0]
fun test(): String
// CHECK JVM_IR:
// Mangled name: #test(){}kotlin.String#<anonymous>#static(){}kotlin.String
// CHECK JS_IR NATIVE:
// Mangled name: #test(){}#<anonymous>#static(){}
local fun <anonymous>(): String