promise icon indicating copy to clipboard operation
promise copied to clipboard

Light and type-safe binding to JS promises

Results 16 promise issues
Sort by recently updated
recently updated
newest added

Reason started supporting let* and let+ operators in latest release and thanks to melange we can use it in latest ocaml and ultimately bucklescript. I'd like to request a promise...

reasoin-promise needs to stay in Reason syntax for a while. However, as people switch to newer versions of BuckleScript, it should probably switch to ReScript syntax.

Is there an example of this library being used in native? Thanks

From Discord: > nitpicking, you could save a line by binding `login` directly as a reason-promise: > > ```reason > external login: unit => Promise.Js.t(authResponse, Js.Promise.error) = "login" > ```...

...it should have been failing [here](https://github.com/aantron/promise/commit/681d58b879ff6a9ef5b86d61dfd26e389bdb760e#diff-a8d77ef5aad99ea3e0ca9ba334be6a95L280). It was possible to change it to a check that the promise is resolved without changing the underlying code (the commit changed only the...

low priority

I realise that the let bindings replaces them rather elegantly in most situations But I am personally a very mix and match-y type where my JS codebases uses promise chains...

See https://github.com/facebook/reason/pull/2487.

blocked

Native `Promise` will still be usable with Reason. This will just make the library lighter to install for projects using OCaml syntax.

low priority