You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In particular, if we try to resolve MyListAlias the @JvmSuppressWildcards annotation is now missing (I'm just printing the toString() here since it's easier, but actually getting the annotations from the type arguments gives the same result):
// Prints: List<MyType> instead of List<[@JvmSuppressWildcards] MyType>println("${(method.returnType().declaration asKSTypeAlias).type.resolve()}")
I've also checked that all annotations get dropped, not just @JvmSuppressWildcards.
I'm guessing this is related to the nested typealias, because the following cases with a single typealias seem to work fine:
interfaceMyTypetypealiasMyListAlias=List<@JvmSuppressWildcards MyType>funmethod(): MyListAlias// This works!// Prints: List<[@JvmSuppressWildcards] MyType>println("${(method.returnType().declaration asKSTypeAlias).type.resolve()}")
interfaceMyTypetypealiasMyAlias=MyTypefunmethod(): List<@JvmSuppressWildcardsMyAlias>
// This works!// Prints: List<[@JvmSuppressWildcards] MyType>println("${(method.returnType().declaration asKSTypeAlias).type.resolve()}")
The text was updated successfully, but these errors were encountered:
We ran into a case in Dagger where the
@JvmSuppressWildcards
is missing in the following case:In particular, if we try to resolve
MyListAlias
the@JvmSuppressWildcards
annotation is now missing (I'm just printing thetoString()
here since it's easier, but actually getting the annotations from the type arguments gives the same result):I've also checked that all annotations get dropped, not just
@JvmSuppressWildcards
.I'm guessing this is related to the nested
typealias
, because the following cases with a singletypealias
seem to work fine:The text was updated successfully, but these errors were encountered: