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
650 B
Kotlin
Vendored
21 lines
650 B
Kotlin
Vendored
// CHECK JS_IR NATIVE:
|
|
// Mangled name: #testEqeq(<dynamic>){}
|
|
// Public signature: /testEqeq|-1993622698448833276[0]
|
|
fun testEqeq(d: dynamic): Boolean
|
|
|
|
// CHECK JS_IR NATIVE:
|
|
// Mangled name: #testEqeqeq(<dynamic>){}
|
|
// Public signature: /testEqeqeq|6434412038753944189[0]
|
|
fun testEqeqeq(d: dynamic): Boolean
|
|
|
|
// CHECK JS_IR NATIVE:
|
|
// Mangled name: #testExclEq(<dynamic>){}
|
|
// Public signature: /testExclEq|-2117076107258151936[0]
|
|
fun testExclEq(d: dynamic): Boolean
|
|
|
|
// CHECK JS_IR NATIVE:
|
|
// Mangled name: #testExclEqeq(<dynamic>){}
|
|
// Public signature: /testExclEqeq|5516019862167337768[0]
|
|
fun testExclEqeq(d: dynamic): Boolean
|
|
|