Antonio Nuno Monteiro

@sync that's pretty amazing, and looks like problem solved when using now.sh, but this would still be needed for people wanting to try out their lambdas that are going to...

@hcarty what do you mean? edit: sorry I hadn't seen @jordwalke's comment.

@jordwalke I personally don't mind it, here are my thoughts on the tradeoffs: - `=\>` is _uglier_ (subjective) but feels natural given `/\*` for example - `=\>` could probably just...

@jordwalke do you agree with the above? should we go ahead and keep `=\>` then?

@jordwalke I really like your 2nd idea. I'll try to prototype something in this PR over the next couple of days. I think you said in Discord that backslash prefixed...

@hcarty the idea I have in mind (and I think it's what Jordan implied) is that `\` could be a prefix for all such transformations between OCaml and Reason. Therefore,...

@jordwalke I think this is ready for another look. I implemented your suggestion by having any operator preceded with a backslash (`\`) be the same operator on the OCaml side...

@hcarty The problem is only about OCaml -> Reason, not the other way around. Some examples: ```shell # Reason -> Reason $ echo 'let (\=>) = (a, b) => a...

The PR isn't done yet, and I haven't found the time to squeeze it in.

I don't think this is a bug. We did switch the representation, but it's "correct" now. Is the BuckleScript contract that the generated JS names can be relied upon? If...