From: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
To: Spiros Eliopoulos <seliopou@gmail.com>
Cc: OCaml <caml-list@inria.fr>
Subject: Re: [Caml-list] ANN: angstrom
Date: Mon, 25 Jul 2016 18:21:19 +0200 [thread overview]
Message-ID: <7DF0D33A403A4B41A5E2AAEAA6F6E06E@erratique.ch> (raw)
In-Reply-To: <CAEkQQgK-=6Z-mrakRwfLpQJV7-fHn588EgbC7aHVb80tdhFpcg@mail.gmail.com>
Le lundi, 25 juillet 2016 à 18:07, Spiros Eliopoulos a écrit :
> So in this situation, the main parse succeeds with errors corrections that are going to be logged somewhere. If something besides logging would be done with the errors, it would fall into one of the other cases described above. The latency difference is on the order of milliseconds, maybe seconds, depending on the application. It's not nearly enough time to make a difference in whatever log analysis process they would be fed into, whether it's inspection by a human (certainly) or some other automated process (they all typically include a ton of latency already).
You are making a lot of assumptions about how the client should use the library or what humans are supposed to tolerate… Giving back control to the client in case of error and allow it to restart the process allows to lift the constraints you put on the client.
Best,
Daniel
next prev parent reply other threads:[~2016-07-25 16:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-22 13:35 Spiros Eliopoulos
2016-07-22 14:38 ` Daniel Bünzli
2016-07-22 21:46 ` Spiros Eliopoulos
2016-07-23 2:17 ` Daniel Bünzli
2016-07-23 6:41 ` Cole Brown
2016-07-23 11:37 ` Daniel Bünzli
2016-07-25 14:15 ` Spiros Eliopoulos
2016-07-25 15:44 ` Daniel Bünzli
2016-07-25 16:07 ` Spiros Eliopoulos
2016-07-25 16:21 ` Daniel Bünzli [this message]
2016-07-25 19:37 ` Spiros Eliopoulos
2016-07-25 20:03 ` Daniel Bünzli
2016-10-13 12:42 ` Anil Madhavapeddy
2017-02-03 19:37 ` Hendrik Boom
2017-02-04 16:36 ` Spiros Eliopoulos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7DF0D33A403A4B41A5E2AAEAA6F6E06E@erratique.ch \
--to=daniel.buenzli@erratique.ch \
--cc=caml-list@inria.fr \
--cc=seliopou@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).