Re: [MirageOS-devel] Lwt NOT deprecated

[Richard Mortier <Richard.Mortier@xxxxxxxxxxxxxxxx>]

On 2 Jul 2014, at 15:21, Vincent Balat <vincent.balat@xxxxxxxxxxxxxxxxxxxxx> 
wrote:

> I'm sending this quick e-mail to deny the rumours that have been heard on 
> this 
> list:

given how pervasively Lwt is currently used in mirage, i think there'd have 
been far more general panic^H^H^H^H^Hinterest if we'd thought Lwt was suddenly 
going away :)

i think the "rumour" (one email, pretty quickly quashed by several responses :) 
was triggered by simple misinterpretation of a discussion connected with a 
decision taken by the Frenetic team to discontinue their support for Lwt in 
favour of Async. (i am unaware of their reasons-- if anyone from Frenetic is on 
the list, it would be great if they could comment!)

having said all that, given the current situation (Mirage mostly using Lwt and 
Frenetic using Async), any further suggestions for/experiences of trying to 
integrate between libraries using a mixture of Lwt and Async would be welcome. 

eg., better to port to one or the other? is it relatively easy to abstract 
across them both? thoughts on how big is the minimal subset of Mirage that 
would need to be ported/abstracted to use Async?  pointers to any documentation 
discussing the tradeoffs between Async and Lwt would also be useful. i've come 
across the wg-parallel list which appeared to be briefly active last year, as 
well as <https://github.com/janestreet/lwt-async> which appears likely to be 
related to the discussion.

thanks!

-- 
Cheers,

R.

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel