Never heard of it before, thanks!
It would be great it you could play the intermediary between dune and the compiler, as you did for the -Ihidden RFC. I think it needs people with their foot in both groups to continue making progress.
Imho dune turning on a wide range of warnings and making them errors has been overall a win for the ecosystem. It forces us to be more disciplined in dealing with code quality issues. I would push back on the idea that dune builds break by themselves. If a build breaks without an explicit upgrade, that is giving us valuable feedback that the build is not reproducible. If it breaks after an explicit upgrade, then the human who did the upgrade should figure out how to fix it (or suppress the warning if not).
For production codebases that must be maintained over time, strict warnings as errors is a godsend. Just look at Go, this is one of the things they got very right.
5 Likes
The issue with warnings isn’t a good example to generalize. We sleep walked into this situation while we were busy frantically turning jbuilder into a build system usable by most OCaml projects from its humble start as a build system for JST’s public projects. After the work was done, the mistake was realized. Though it was already too late to change things without causing a lot of breakage.
Thanks for the link regarding namespaces. We intend to add whatever build system support is necessary if you ever get around to implementing it.