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
363 B
Kotlin
Vendored
19 lines
363 B
Kotlin
Vendored
// FIR_IDENTICAL
|
|
|
|
// MUTE_SIGNATURE_COMPARISON_K2: JVM_IR
|
|
// ^ KT-57433, KT-57429
|
|
|
|
package test
|
|
|
|
class Foo<T> {
|
|
inner class Inner<P>(val a: T, val b: P)
|
|
}
|
|
|
|
inline fun <A, B> foo(a: A, b: B, x: (A, B) -> Foo<A>.Inner<B>): Foo<A>.Inner<B> = x(a, b)
|
|
|
|
fun box(): String {
|
|
val z = Foo<String>()
|
|
val foo = foo("O", "K", z::Inner)
|
|
return foo.a + foo.b
|
|
}
|