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
27 lines
728 B
Kotlin
Vendored
27 lines
728 B
Kotlin
Vendored
// CHECK:
|
|
// Mangled name: {}p
|
|
// Public signature: /p|6715504260787941082[0]
|
|
var p: Int
|
|
// CHECK JVM_IR:
|
|
// Mangled name: #<get-p>(){}kotlin.Int
|
|
// Public signature: /p.<get-p>|5329635969197638839[0]
|
|
// CHECK JS_IR NATIVE:
|
|
// Mangled name: #<get-p>(){}
|
|
// Public signature: /p.<get-p>|-1162552463316289847[0]
|
|
get
|
|
// CHECK:
|
|
// Mangled name: #<set-p>(kotlin.Int){}
|
|
// Public signature: /p.<set-p>|-6346582004572228570[0]
|
|
set
|
|
|
|
// CHECK:
|
|
// Mangled name: #testProperty(){}
|
|
// Public signature: /testProperty|5285658686723604291[0]
|
|
fun testProperty(): Unit
|
|
|
|
// CHECK:
|
|
// Mangled name: #testVariable(){}
|
|
// Public signature: /testVariable|660968387512033895[0]
|
|
fun testVariable(): Unit
|
|
|