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
693 B
Kotlin
Vendored
21 lines
693 B
Kotlin
Vendored
// CHECK JVM_IR:
|
|
// Mangled name: #testEqeq(kotlin.Int;kotlin.Int){}kotlin.Boolean
|
|
// Public signature: /testEqeq|-8467980441682237872[0]
|
|
fun testEqeq(a: Int, b: Int): Boolean
|
|
|
|
// CHECK JVM_IR:
|
|
// Mangled name: #testEquals(kotlin.Int;kotlin.Int){}kotlin.Boolean
|
|
// Public signature: /testEquals|-6776844626244337538[0]
|
|
fun testEquals(a: Int, b: Int): Boolean
|
|
|
|
// CHECK JVM_IR:
|
|
// Mangled name: #testJEqeqNull(){}kotlin.Boolean
|
|
// Public signature: /testJEqeqNull|-16498498668551755[0]
|
|
fun testJEqeqNull(): Boolean
|
|
|
|
// CHECK JVM_IR:
|
|
// Mangled name: #testJEqualsNull(){}kotlin.Boolean
|
|
// Public signature: /testJEqualsNull|1794297066470075977[0]
|
|
fun testJEqualsNull(): Boolean
|
|
|