Re: [Caml-list] Question about Lwt/Async

["Milan Stanojević" <milanst@gmail.com>]

> Most people provide this internally for each of their projects, e.g.
> Cohttp's IO signature. However, we have quite a few projects that needed
> this abstraction, so duplicating this code in each repo seemed wrong. Thus
> we developed future, which was recently released in opam.

I didn't check opam but I guess there are libraries that are just
Async or (more likely) just Lwt. If I want to use them both I'm out of
luck, right?

I'd rather try to do something like Yaron said and have Lwt run using
Async backend or vice versa. Both are probably possible. Converting
between Lwt.t and Deferred.t in that case is trivial.

This would allow us then to mix Async and Lwt libraries in the same
application, and programmers would be free to choose to have their
interface be Async or Lwt,  or both if abstracting layer works
for them.

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.