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
13 lines
450 B
Kotlin
Vendored
13 lines
450 B
Kotlin
Vendored
// CHECK:
|
|
// Mangled name: #foo(){}
|
|
// Public signature: /foo|-1041209573719867811[0]
|
|
fun foo(): Unit
|
|
|
|
// CHECK JVM_IR:
|
|
// Mangled name: #useMemo(kotlin.Function0<0:0>){0§<kotlin.Any?>}0:0
|
|
// Public signature: /useMemo|-5878263003233931724[0]
|
|
// CHECK JS_IR NATIVE:
|
|
// Mangled name: #useMemo(kotlin.Function0<0:0>){0§<kotlin.Any?>}
|
|
// Public signature: /useMemo|-3060604648637761528[0]
|
|
fun <T : Any?> useMemo(callback: Function0<T>): T
|