Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Future of js-promises branch #647
There are some plans for being able to run Lwt and Repromise in one process on the native side in the future, to be able to take advantage of all the native libraries based on Lwt.
The other way is by binding to libuv, which is the C library that implements Node's I/O, and then having that binding drive both Lwt and Repromise. Here is such a binding, and sample code showing Lwt and Repromise being used together.
Indeed, I'm having a great time using Repromise in some front-end projects (in Reason). But another project I'm building entirely in OCaml has a large native codebase that heavily relies on Uwt and Lwt, in which I'm sharing code between front-end and backend.
I'm aware of the unsoundness of JS promises, what I'm after are the semantics of the Lwt library itself which I like and built many utilities around. I also rely heavily on modules such as
I'd be interested in, and would love to help with, an approach that goes the other way around, if