From: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
To: Dario Teixeira <dario.teixeira@nleyten.com>
Cc: Rudi Grinberg <rudi.grinberg@gmail.com>, caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] Functorising over Cohttp's backends
Date: Mon, 29 Aug 2016 23:51:55 +0200 [thread overview]
Message-ID: <1EA71190C2C049079BE32A69F18ABB9C@erratique.ch> (raw)
In-Reply-To: <c99c0fc01ea0bc77cc88eca25701847b@nleyten.com>
On Monday 29 August 2016 at 20:42, Dario Teixeira wrote:
> Cohttp is perhaps the poster child for how the Lwt/Async schism
> makes many APIs way more complex than they should be! (Not that
> there's an easy solution to this situation...)
I'd rather say it is the poster child on how not to cope with the lwt/async schism... Don't functorize over IO, provide non-blocking abstractions that can be used with either.
D
next prev parent reply other threads:[~2016-08-29 21:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-29 13:53 Dario Teixeira
2016-08-29 15:39 ` Rudi Grinberg
2016-08-29 18:42 ` Dario Teixeira
2016-08-29 21:51 ` Daniel Bünzli [this message]
2016-08-30 9:08 ` Malcolm Matalka
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=1EA71190C2C049079BE32A69F18ABB9C@erratique.ch \
--to=daniel.buenzli@erratique.ch \
--cc=caml-list@inria.fr \
--cc=dario.teixeira@nleyten.com \
--cc=rudi.grinberg@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