azalea/kotlin-fork
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[IR] Dump IdSignatures and mangled names in irText tests

Browse Source 
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
Download Patch File Download Diff File Expand all files Collapse all files
compiler/testData/ir/irText/expressions/extFunSafeInvoke.sig.kt.txt
Vendored
+8
View File
@@ -0,0 +1,8 @@
// 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?