We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This is a case in XProcessing. Not sure if it's an intended change. With classes like:
interface Usage : Foo<Long, Integer> { fun foo(param: Foo<Double, Integer>): Foo<String, Integer> } interface Foo<V1, V2: Integer> : Bar<Baz<V1, Number>, V2> {} interface Bar<U1, U2: Integer> : Baz<U1, U2> {} interface Baz<T1, T2: Number> { fun method1(): T1 fun method2(): T2 }
And getting the return type of method1.asMemberOf(UsageType) we get U1 in KSP2 but Baz<Long, Number> in KSP1.
method1.asMemberOf(UsageType)
U1
Baz<Long, Number>
Repro: kuanyingchou@e3414b9
The text was updated successfully, but these errors were encountered:
neetopia
Successfully merging a pull request may close this issue.
This is a case in XProcessing. Not sure if it's an intended change. With classes like:
And getting the return type of
method1.asMemberOf(UsageType)
we getU1
in KSP2 butBaz<Long, Number>
in KSP1.Repro: kuanyingchou@e3414b9
The text was updated successfully, but these errors were encountered: