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
Currently, even for regular usages, Json operates in two modes -- streaming-based decoding and, in the case of polymorphism, JsonElement-based decoding.
The latter complicates maintainability, predictability of code execution and debuggability (e.g. printing proper error reporting, toString, code bloating and a separate-code path used for polymorphism-unrelated functionality).
My proposal is to completely get rid of tree-based deciding on the path of decodeFromString and decodeFromSteam and maintain it only for JsonElement serialization
The text was updated successfully, but these errors were encountered:
Currently, even for regular usages,
Json
operates in two modes -- streaming-based decoding and, in the case of polymorphism,JsonElement
-based decoding.The latter complicates maintainability, predictability of code execution and debuggability (e.g. printing proper error reporting,
toString
, code bloating and a separate-code path used for polymorphism-unrelated functionality).My proposal is to completely get rid of tree-based deciding on the path of
decodeFromString
anddecodeFromSteam
and maintain it only forJsonElement
serializationThe text was updated successfully, but these errors were encountered: