(I know non-Multicore devs are frozen at the moment, but just to get the dicussion started...)
The fact that the compiler does not install META files is a source of problems for the two main consumers of this metadata: ocamlfind and dune. In fact, both tools include their own set of META definitions for these libraries to avoid depending on each other. This leads to tricky bugs from time to time as well as adding friction due to the need to keep them in sync with each other and with the library definitions.
Having the compiler install META files for its own libraries would cleanly solve this issue, and would be a small change at that. I don't see any outright downsides to doing so.
Opinions?
cc @jeremiedimino
(I know non-Multicore devs are frozen at the moment, but just to get the dicussion started...)
The fact that the compiler does not install META files is a source of problems for the two main consumers of this metadata:
ocamlfindanddune. In fact, both tools include their own set of META definitions for these libraries to avoid depending on each other. This leads to tricky bugs from time to time as well as adding friction due to the need to keep them in sync with each other and with the library definitions.Having the compiler install META files for its own libraries would cleanly solve this issue, and would be a small change at that. I don't see any outright downsides to doing so.
Opinions?
cc @jeremiedimino