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
17 lines
827 B
Kotlin
Vendored
17 lines
827 B
Kotlin
Vendored
// CHECK JVM_IR:
|
|
// Mangled name: #testD(kotlin.Comparable<kotlin.Double>;kotlin.Comparable<kotlin.Double>){}kotlin.Boolean
|
|
// Public signature: /testD|-8334682674453061094[0]
|
|
// CHECK JS_IR NATIVE:
|
|
// Mangled name: #testD(kotlin.Comparable<kotlin.Double>;kotlin.Comparable<kotlin.Double>){}
|
|
// Public signature: /testD|6420307726503450357[0]
|
|
fun testD(x: Comparable<Double>, y: Comparable<Double>): Boolean
|
|
|
|
// CHECK JVM_IR:
|
|
// Mangled name: #testF(kotlin.Comparable<kotlin.Float>;kotlin.Comparable<kotlin.Float>){}kotlin.Boolean
|
|
// Public signature: /testF|2241994539085447467[0]
|
|
// CHECK JS_IR NATIVE:
|
|
// Mangled name: #testF(kotlin.Comparable<kotlin.Float>;kotlin.Comparable<kotlin.Float>){}
|
|
// Public signature: /testF|5734029490201124122[0]
|
|
fun testF(x: Comparable<Float>, y: Comparable<Float>): Boolean
|
|
|