Conversation
These conflicts with the let async ident = ... extension. They are still available in method positions. What should we do?
|
OCaml supports |
|
It's a very nice surprise that Reason's syntax enabled us to omit the A couple of thoughts: We would probably want to start with make omitting the For some reason it's failing on Mac OS only with " Error: 8 states have shift/reduce conflicts." |
|
The conflicts are due to the patch forcing parentheses around |
|
Wow. This would really be the killer feature of the Reason syntax, IMO. Well, assuming the BuckleScript team relaxes its position on AST modification. 🤣 |
|
ummm I have strong reservations about elevating ppx extension points to this level of "prominence" in the syntax. I believe it should be fairly "loud" when a syntax transform is happening. |
|
@jaredly There are a few relevant active PRs upstream which may be of interest and worth chiming in on to make sure the Reason community's needs are taken into account. Monadic
|
|
@hcarty wow, that's a very cool proposal! |
Allow extension sugar without having to put
%:The sugar applies for any lowercase identifier that is not a keyword.
The
let f() = .../let f() { ... }syntax had to be removed (functions are now always bound like any other expressions,let f = () => ...).