Gabriel Scherer

Note: currently choices based on the representation (or not) of constructors are made during the translation from Typedtree to Lambda, in particular during pattern-matching compilation. If we wanted to keep...

I think that we should wait a bit for things to cool down, and start by looking around if someone else wants to push this work. (note that removing an...

Another aspect to have in mind is possible internationalization of error messages in the future. On Fri, Sep 23, 2022 at 1:27 PM Daniel Bünzli ***@***.***> wrote: > What's wrong...

For the record: @Octachron and myself intended this RFC to be the basis for an Outreachy internship, but we ended up without an intern to work on this. If someone...

People have (rightly) suggested that the error identifier could/should be a clickable link going to a webpage with documentation about the error. I wasn't sure how to include clickable links...

My impression is that "showing the error code, with the appropriate escape codes to have a clickable link" and "showing a URL" are two reasonable approaches with pros and cons,...

## Alternative proposal I have also been interested in Lionel Parreaux UCS work, and made a weird proposal that is as expressive as pattern guards in the 2019 blog post...

Note: previous RFC https://github.com/ocaml/RFCs/pull/12 is also relevant prior work.

Another relevant previous work is the work on pattern guards for Successor ML, see https://github.com/JohnReppy/compiling-pattern-guards . The syntax that they propose is also "bad" in the sense that it encourages...

One question that is delicate and deserves careful discussion is whether `| p and e with ` should enforce the `` part to be exhaustive (with an exhaustivity warning otherwise),...