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
19 lines
453 B
Kotlin
Vendored
19 lines
453 B
Kotlin
Vendored
// FIR_IDENTICAL
|
|
// This test can be removed as soon as the compiler stops supporting language version 1.5.
|
|
// !LANGUAGE: -ProhibitJvmFieldOnOverrideFromInterfaceInPrimaryConstructor
|
|
// SKIP_KT_DUMP
|
|
// SKIP_KLIB_TEST
|
|
// TARGET_BACKEND: JVM_IR
|
|
// WITH_STDLIB
|
|
|
|
// MUTE_SIGNATURE_COMPARISON_K2: ANY
|
|
// ^ KT-57429
|
|
|
|
interface A { val x: Int }
|
|
|
|
class B(@JvmField override val x: Int): A
|
|
|
|
class C<D: A>(@JvmField val d: D)
|
|
|
|
class E(c: C<B>) { val ax = c.d.x }
|