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
32 lines
1.0 KiB
Kotlin
Vendored
32 lines
1.0 KiB
Kotlin
Vendored
package interop
|
|
|
|
// CHECK:
|
|
// Mangled name: interop.Definitions
|
|
// Public signature: interop/Definitions|null[0]
|
|
object Definitions {
|
|
// CHECK:
|
|
// Mangled name: interop.Definitions{}ktValue
|
|
// Public signature: interop/Definitions.ktValue|-7932704459611172354[0]
|
|
val ktValue: String
|
|
// CHECK JVM_IR:
|
|
// Mangled name: interop.Definitions#<get-ktValue>(){}kotlin.String
|
|
// Public signature: interop/Definitions.ktValue.<get-ktValue>|233367925131846588[0]
|
|
get
|
|
|
|
// CHECK:
|
|
// Mangled name: interop.Definitions#<init>(){}
|
|
// Public signature: interop/Definitions.<init>|-5645683436151566731[0]
|
|
private constructor() /* primary */
|
|
|
|
// CHECK:
|
|
// Mangled name: interop.Definitions{}KT_CONSTANT
|
|
// Public signature: interop/Definitions.KT_CONSTANT|-8714407162660026641[0]
|
|
const val KT_CONSTANT: String
|
|
// CHECK JVM_IR:
|
|
// Mangled name: interop.Definitions#<get-KT_CONSTANT>(){}kotlin.String
|
|
// Public signature: interop/Definitions.KT_CONSTANT.<get-KT_CONSTANT>|4728854297559730352[0]
|
|
get
|
|
|
|
}
|
|
|