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
30 lines
861 B
Kotlin
Vendored
30 lines
861 B
Kotlin
Vendored
package test
|
|
|
|
// CHECK:
|
|
// Mangled name: test.Host
|
|
// Public signature: test/Host|null[0]
|
|
object Host {
|
|
// CHECK:
|
|
// Mangled name: test.Host#<init>(){}
|
|
// Public signature: test/Host.<init>|-5645683436151566731[0]
|
|
private constructor() /* primary */
|
|
|
|
// CHECK JVM_IR:
|
|
// Mangled name: test.Host#foo(){0§<kotlin.Any?>}kotlin.String
|
|
// Public signature: test/Host.foo|-170825690606698604[0]
|
|
// CHECK JS_IR NATIVE:
|
|
// Mangled name: test.Host#foo(){0§<kotlin.Any?>}
|
|
// Public signature: test/Host.foo|-7822584347064313243[0]
|
|
inline fun <reified T : Any?> foo(): String
|
|
|
|
}
|
|
|
|
// CHECK JVM_IR:
|
|
// Mangled name: test#test(){}kotlin.String
|
|
// Public signature: test/test|-7008832412320199001[0]
|
|
// CHECK JS_IR NATIVE:
|
|
// Mangled name: test#test(){}
|
|
// Public signature: test/test|6620506149988718649[0]
|
|
fun test(): String
|
|
|