Morning guys, We have an interesting use case of g...

# android

[Issa]

Morning guys,
We have an interesting use case of generics in kotlin:

import kotlin.reflect.KClass

fun main() {
    doSomething(B::class, C::class)
}

fun <T : A> doSomething(vararg dialogClasses: KClass<T>) {
    // no-op
}

open class A

class B : A()

class C : A()

the compiler complains about the second argument of doSomething() function even if it is a sub-type of A. Is there any reason for this complaint?
How can this issue can be solved?

[ti4n]

fun doSomething(vararg dialogClasses: KClass<out A>) {
    // no-op
}

try this

[Issa]

yep that worked Thanks @ti4n

[Asagald]

And if you wanted to learn more about how it works (and why), you can check out this kotlin doc: https://kotlinlang.org/docs/generics.html

[Willy Ricardo]

doSomething<A>(B::class, C::class)

[gabrielfv]

I think compiler/linter could infer that. Effectively fun <T : A> doSomething(...) is different from fun doSomething(... KClass<out A>). But yeah, in this scenario it seems pretty clear @ti4n suggestion is the desired behavior