Consider moving reified overload of encodeTo and decodeFrom* into popular formats
#2850
Assignees
Labels
Comments
sandwwraith
added a commit
that referenced
this issue
Nov 8, 2024
…treamline experience for newcomers. decodeFromString was already there for @FormatLanguage reasons. Fixes #2850
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Otherwise, the tooling starts crumbling and suggesting wrong overloads with lack of discoverability.
Also, things like
Json.encodeToString(foo)andJson.encodeToString(FooSerializer, foo)live in different packages, providing weird autocompletion side-effects (when tab- based completion accidentally import the wrong method)The text was updated successfully, but these errors were encountered: