Florian Angeletti

Why do you want to enable this warning for the compiler? In particular after a quick glance, there are many instance where in order to avoid the syntactic overhead of...

It is not possible to introduce only one field or constructor in scope? Since this is matter of changing the coding style of the repository, l don't think that a...

A regexp of ascii-compatible characters will only have the same meaning for an unicode-aware and ascii-only regexp engine when applied to sequence of ascii-only characters. The issue on non-ascii text...

I don't think that this kind of link would be useful: you cannot expect that people will have the time to read an unicode committee report before using the `Str`...

I disagree that it is important to keep the same version of Menhir when updating the parser? The generated parser is a build artifact committed in the tree to avoid...

I don't think anyone rely on the specific format of the `with_camltex` variable in `Makefile.config`. The `caml-tex` tool is never installed and the variable only matters when building the manual.

Moving the variable to `Makefile.build_config.in` is definitively a good idea. Renaming `caml-tex` to `ocamltex` seems fine since it fits with the various *tex tools.

Beyond the rewriting of the Makefile conditionals, I think that having an explicitly named variables for the status of optional libraries (`lib_$libname`) and optional tools (`build_$toolname`) is an improvement. The...

I removed the 4.11 milestone since this specific problem has been surgically removed for now.

Concerning the alpha business, all fixes are still in scope for 5.0 during the alpha and beta release phase. Please don't hesitate to ping me on PRs that should be...