In the grand scheme of things, how bad of an idea ...
# serialization
e
In the grand scheme of things, how bad of an idea is it to use
KClass<T>.serializer(): KSerializer<T>
?
r
I've been using this long time ago in my KVision project as kind of "last resort", but because of issues on Kotlin/JS (e.g. https://github.com/Kotlin/kotlinx.serialization/issues/113) I've stopped using this.