Jared Forsyth
Jared Forsyth
@jchavarri ok I added sandboxes, so now this script works with both 4.02 and 4.06! Very clean
Ok @jordwalke @ulrikstrid @jchavarri I think this is good to go!
Hmmm actually I'm thinking that all I really need is `ppx_let` https://github.com/janestreet/ppx_let with the proper setup. Unfortunately it looks like reason doesn't support the 4.03 `let%ext` syntax :(
Actually, I've got a ppx together that isn't tied to any specific async implementation, as long as it adheres to a general signature.
For the record, here's the blog post I wrote on this subject recently: https://jaredforsyth.com/2017/12/30/building-async-await-in-reason/ (and accompanying ppx https://github.com/jaredly/reason_async) It touches on many of the topics discussed here. (I'm also rather...
@danny-andrews-snap I know there can be elegance to treating all monads the same, but I think async/await and optional chaining are pretty compelling specializations (in javascript and rust, respectively). to...
See also #1321
I'm confused at what this changes. Could you clarify in the description, what the transformation ends up being? I expect this to transform to ``` e->ReactEvent.Form.target##value a->f(c)->Js.log; a->f(~named, ~bar)->g(~z, ())->Js.log...
Ah ok, that makes sense :) Sounds great!
exporting a more abstracted version is not yet supported. I could imagine using an attribute w/ an "export type" to do that kind of thing, but yeah I think that...