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
45 lines
798 B
Kotlin
Vendored
45 lines
798 B
Kotlin
Vendored
// FIR_IDENTICAL
|
|
// TARGET_BACKEND: JVM
|
|
|
|
// MUTE_SIGNATURE_COMPARISON_K2: ANY
|
|
// ^ KT-57429
|
|
|
|
// FILE: samConversionInGenericConstructorCall.kt
|
|
fun test3(
|
|
f1: (String) -> String,
|
|
f2: (Int) -> String
|
|
) =
|
|
C(f1).D(f2)
|
|
|
|
class Outer<T1>(val j11: J<T1, T1>) {
|
|
inner class Inner<T2>(val j12: J<T1, T2>)
|
|
}
|
|
|
|
fun test4(f: (String) -> String, g: (Any) -> String) = Outer(f).Inner(g)
|
|
|
|
fun testGenericJavaCtor1(f: (String) -> Int) = G(f)
|
|
|
|
fun testGenericJavaCtor2(x: Any) {
|
|
x as (String) -> Int
|
|
G(x)
|
|
}
|
|
|
|
// FILE: J.java
|
|
public interface J<T1, T2> {
|
|
T1 foo(T2 x);
|
|
}
|
|
|
|
// FILE: C.java
|
|
public class C<X> {
|
|
public C(J<X, X> jxx) {}
|
|
|
|
public class D<Y> {
|
|
public D(J<X, Y> jxy) {}
|
|
}
|
|
}
|
|
|
|
// FILE: G.java
|
|
public class G<TClass> {
|
|
public <TCtor> G(J<TCtor, TClass> x) {}
|
|
}
|