Replies: 1 comment 1 reply
-
There should be versions of those methods that take a serializer - that's the one you want to use if you want to avoid the reified type |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
These methods have only
inline fun <reified T>
versions of them which severely limits their usability in kotlin code since you either have to call them with a concrete type or you have to propagateinline
up into your code (which then cannot be virtual, etc).I think they should have a
KClass<T>
version of them so they can be used with generics in kotlin.This is how it could look like:
I don't really know if it is even possible, but from user's perspective it sure is needed. I opened it first as an disscussion in case it is a complete nonsense.
Beta Was this translation helpful? Give feedback.
All reactions