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
21 lines
662 B
Kotlin
Vendored
21 lines
662 B
Kotlin
Vendored
package test
|
|
|
|
// CHECK:
|
|
// Mangled name: test#foo(kotlin.Function0<kotlin.Unit>){}
|
|
// Public signature: test/foo|251397761749529488[0]
|
|
inline fun foo(x: Function0<Unit>): Unit
|
|
|
|
// CHECK JVM_IR:
|
|
// Mangled name: test#id@kotlin.String(kotlin.String;kotlin.IntArray...){}kotlin.String
|
|
// Public signature: test/id|-8103162913932729860[0]
|
|
// CHECK JS_IR NATIVE:
|
|
// Mangled name: test#id@kotlin.String(kotlin.String;kotlin.IntArray...){}
|
|
// Public signature: test/id|58840929144244075[0]
|
|
fun String.id(s: String, vararg xs: Int): String
|
|
|
|
// CHECK:
|
|
// Mangled name: test#test(){}
|
|
// Public signature: test/test|6620506149988718649[0]
|
|
fun test(): Unit
|
|
|