Browse thread
Recursion on React.events.
[
Home
]
[ Index:
by date
|
by threads
]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
| Date: | -- (:) |
| From: | Jérémie Dimino <jeremie@d...> |
| Subject: | Re: [Caml-list] Re: Recursion on React.events. |
Le jeudi 10 décembre 2009 à 23:24 +0100, Guillaume Yziquel a écrit : > Yes. It's also here where I worry about a few things concerning Lwt: > > In Lwt, you have a monadic way to do context switches for multithreading > withing a single real thread. So if you use Lwt inside the update cycle, > you could well jump out of the update cycle with a Lwt context switch. > As long as you do not encounter a Lwt construct within definition of > signals and events, you can be pretty sure that the update cycle will go > through to its end without using Lwt inside an event/signal. But at the > same time, it seems that the monadic way Lwt is built avoids us such > problems. But I may be mistaken. It is possible to use Lwt inside an update cycle. It is not a problem to switch context in an update cycle as long as you respect React's rules. > So the compatibility of Lwt and React seems to me a worthwile question > if one wants to use OCaml for high availability, reactive, parallel > computations. And in this context, making E/S.switch easy to use would > quite important... Thanks to React being lowlevel, the two libraries are compatible out of the box. Jérémie