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
35 lines
710 B
Kotlin
Vendored
35 lines
710 B
Kotlin
Vendored
// MUTE_SIGNATURE_COMPARISON_K2: ANY
|
|
// ^ KT-57754
|
|
|
|
interface IBase {
|
|
fun foo(x: Int, s: String)
|
|
fun bar(): Int
|
|
fun String.qux()
|
|
}
|
|
|
|
object BaseImpl : IBase {
|
|
override fun foo(x: Int, s: String) {}
|
|
override fun bar(): Int = 42
|
|
override fun String.qux() {}
|
|
}
|
|
|
|
interface IOther {
|
|
val x: String
|
|
var y: Int
|
|
val Byte.z1: Int
|
|
var Byte.z2: Int
|
|
}
|
|
|
|
fun otherImpl(x0: String, y0: Int): IOther = object : IOther {
|
|
override val x: String = x0
|
|
override var y: Int = y0
|
|
override val Byte.z1: Int get() = 1
|
|
override var Byte.z2: Int
|
|
get() = 2
|
|
set(value) {}
|
|
}
|
|
|
|
class Test1 : IBase by BaseImpl
|
|
|
|
class Test2 : IBase by BaseImpl, IOther by otherImpl("", 42)
|