caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Jeremie Dimino <jdimino@janestreet.com>
To: "Milan Stanojević" <milanst@gmail.com>
Cc: Ashish Agarwal <agarwal1975@gmail.com>,
	Yotam Barnoy <yotambarnoy@gmail.com>,
	Simon Cruanes <simon.cruanes.2007@m4x.org>,
	Malcolm Matalka <mmatalka@gmail.com>,
	Ocaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] Question about Lwt/Async
Date: Tue, 8 Mar 2016 10:54:31 +0000	[thread overview]
Message-ID: <CANhEzE7g8-hxH9Z0UUwWKow6Zs2_AMM9QxbXj4KwgTBudvuBWA@mail.gmail.com> (raw)
In-Reply-To: <CAKR7PS_zYihdWOabZBC0PVn+b-N7QRoKQP7BFwjVWsvAfXMRng@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 721 bytes --]

On Tue, Mar 8, 2016 at 6:55 AM, Milan Stanojević <milanst@gmail.com> wrote:

> Of course, devil is in the details. I hope that this is indeed
> possible and that changes necessary to Lwt and Async to make this work
> are not huge.


​Right now we just need a few modifications to Async to make this work (Lwt
using Async backend or vice versa).​

It's relatively easy to get into a state with the limitation that you
couldn't use the same file descriptor with Lwt and Async, which seems
acceptable. For stdout/stderr it'd be fine as long as you don't print at
the same time, in which case the output might be interleaved. But with a
bit more work on Lwt and Async this could be sorted

-- 
Jeremie

[-- Attachment #2: Type: text/html, Size: 1610 bytes --]

  reply	other threads:[~2016-03-08 10:54 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-07  1:38 Yotam Barnoy
2016-03-07  7:16 ` Malcolm Matalka
2016-03-07  9:08   ` Simon Cruanes
2016-03-07 14:06     ` Yotam Barnoy
2016-03-07 14:25       ` Ashish Agarwal
2016-03-07 14:55         ` rudi.grinberg
2016-03-07 14:59           ` Ivan Gotovchits
2016-03-07 15:05             ` Ivan Gotovchits
2016-03-08  6:55         ` Milan Stanojević
2016-03-08 10:54           ` Jeremie Dimino [this message]
2016-03-07 15:16 ` Jesper Louis Andersen
2016-03-07 17:03   ` Yaron Minsky
2016-03-07 18:16     ` Malcolm Matalka
2016-03-07 18:41       ` Yaron Minsky
2016-03-07 20:06         ` Malcolm Matalka
2016-03-07 21:54           ` Yotam Barnoy
2016-03-08  6:56             ` Malcolm Matalka
2016-03-08  7:46               ` Adrien Nader
2016-03-08 11:04               ` Jeremie Dimino
2016-03-08 12:47                 ` Yaron Minsky
2016-03-08 13:03                   ` Jeremie Dimino
2016-03-09  7:35                     ` Malcolm Matalka
2016-03-09 10:23                       ` Gerd Stolpmann
2016-03-09 14:37                         ` Malcolm Matalka
2016-03-09 17:27                           ` Gerd Stolpmann
2016-03-08  9:41     ` Francois Berenger
2016-03-11 13:21     ` François Bobot
2016-03-11 15:22       ` Yaron Minsky
2016-03-11 16:15         ` François Bobot
2016-03-11 17:49           ` Yaron Minsky
2016-03-08  5:59 ` Milan Stanojević

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=CANhEzE7g8-hxH9Z0UUwWKow6Zs2_AMM9QxbXj4KwgTBudvuBWA@mail.gmail.com \
    --to=jdimino@janestreet.com \
    --cc=agarwal1975@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=milanst@gmail.com \
    --cc=mmatalka@gmail.com \
    --cc=simon.cruanes.2007@m4x.org \
    --cc=yotambarnoy@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).