-
-
Notifications
You must be signed in to change notification settings - Fork 160
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Non-side-effecting Read #312
Comments
Hi Peter! This sounds alike a reasonable either (maybe called One issue with uPickle is I do not think it is sufficiently rigorous with what exceptions are thrown, when and why. Trying to stuff it into an |
Yeah, Is that something you'd do soon or do you prefer me to give it a try? Would it suffice to check for |
I won’t have time to take a crack at it any time soon, so go ahead
…On Mon, 1 Jun 2020 at 7:56 PM, peter-empen ***@***.***> wrote:
Yeah, readEither sounds really good, I'm not opinionated. In Circe decode
returns the same.
Is that something you'd do soon or do you prefer me to give it a try?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#312 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAHEB7GXMLETGIT5XC6DU6LRUOJPTANCNFSM4NPW6Q3A>
.
|
OK. |
yes currently read always fails fast with an exception |
|
Closing this as a wontfix together with #317 |
Hi Li,
what is your attitude towards an additional read method that will never throw an exception? I mean a signature like
def maybeRead[T: Reader](s: ujson.Readable): Either[String, T]
where
String
would be the message of the exception you are throwing.Although this is easy to achieve on top of the current read, I still wonder whether it was worth to supply.
The text was updated successfully, but these errors were encountered: