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
Most other Kotlin issues have been resolved (such as object modules requiring @JvmStatic). Is there any chance that this issue is solved too?
Workaround is pretty ugly, especially because it is pretty long and using it forces us to split declarations of injected types into multiple lines.
The text was updated successfully, but these errors were encountered:
matejdro
changed the title
Allow injection in Kotlin without @JvmSuppressWildcards
Allow typed injection in Kotlin without @JvmSuppressWildcards
May 4, 2021
This is something on our list to address, but unfortunately we probably can't do full support in the sense of merging the key space for all parameterized keys due to the way it breaks backwards compatibility, complications with nested types, and complications with bidirectional support (e.g. intuitively we want to make Set<? extends Foo> and Set<Foo> be the same, but you can't actually assign a Set<? extends Foo> to a Set<Foo>.)
Our current plan is to improve the error message with a suggestion of the similar keys if they exist in the binding graph as well as probably doing the same thing as Guice did in google/guice#1366 to make this easier with multibindings.
As per #900 (comment)
Most other Kotlin issues have been resolved (such as object modules requiring
@JvmStatic
). Is there any chance that this issue is solved too?Workaround is pretty ugly, especially because it is pretty long and using it forces us to split declarations of injected types into multiple lines.
The text was updated successfully, but these errors were encountered: