Anton Bachin

There is an absolutely trivial example here: https://github.com/aantron/promise-example-esy. To get this used on the native side, we'd need to make it run with Lwt, probably. There is a version of...

One way to do this is to put into opam release archives ASTs that have already been processed with `refmt`.

Perhaps I won't do this conversion for that reason. I originally created this issue before the announcement of Melange, when it looked like there would be no compiler that used/favored...

> How dare you! My apologies :D Perhaps with Melange there will be good reason, eventually, to "push"/advertise native reason-promise. But there is also the pending merging of effects into...

@TheSpyder I removed the peer dependency completely. I figure anyone using `reason-promise` is going to inevitably depend on `rescript` (or `bs-platform`) anyway, and we don't need an extra nag. I'll...

> I hate to bug you, but can we get that release please? 😅 Now out as [email protected]. Thanks for bugging me. I had lost track of this.

`.await` is the obvious choice for JS familiarity. For some reason, the term never grew on me. I always liked `.async`, even though in JS it is used on the...

Yes, there will have to be a separate suffix for `map`. I haven't tried it yet, but maybe we can do `let.async.map` or similar. Just thinking now, another option, which...

In my experience, in practice, you almost never end up using `map` with `let`-like bindings, because a sequence of `let`s is actually expanded to nested code like this: ``` flatMap(p1,...

@jordwalke I added an experimental `Promise.Let` module in branch `let`: https://github.com/aantron/promise/blob/c85cef9384363ab6ebad03735b19e0d80c963650/src/native/promise.rei#L252-L260 https://github.com/aantron/promise/blob/c85cef9384363ab6ebad03735b19e0d80c963650/src/native/promise.re#L586-L589 It's in Promise native only for now, because I didn't want to mess around with getting a development...