Include -opaque in dev's :standard definition

[craff]

The title says it all: you should not force the user to use a compiler option while you have default and ways to customize them.

[bobot]

Could you be a little more specific? I though the -opaque is used in dev by default. So it should be in :standard.

[nojb]

Could you be a little more specific? I though the -opaque is used in dev by default. So it should be in :standard.

In fact it isn't because -opaque is a little special as it affects the calculation of dependencies (without -opaque the .cmx are dependencies, otherwise they aren't).

[craff]

You can compute dependencies using ocamlc -opaque or ocamldep. Some code like mine relies too much on flambda inlining to use -opaque in dev mode. -opaque is not a problem in bytecode. Le 11 octobre 2021 21:48:24 GMT-10:00, "Nicolás Ojeda Bär" ***@***.***> a écrit :

…

> Could you be a little more specific? I though the `-opaque` is used in dev by default. So it should be in `:standard`. In fact it isn't because `-opaque` is a little special as it affects the calculation of dependencies (without `-opaque` the `.cmx` are dependencies, otherwise they aren't). -- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: #4986 (comment)

[bobot]

@craff I don't understand what you are explaining. To rephrase @nojb, we can't let people remove -opaque in dev mode as easily as changing the flags without doing something for the computation of the dependencies.

I think the need is valid. I think a standardized opt-out would be better than meddling with the flags and dune detecting it. I just don't know at which level we should add it (dune-project, package, stanza).

[ejgallego]

In Coq indeed users can mess with the flags and break the Dune mode as rules won't be updated; I actually thought of at some point indeed having the coq rules analyze the flags and keep the rules in sync [or error], but that's certainly a minor optimization.

[rgrinberg]

I think the need is valid. I think a standardized opt-out would be better than meddling with the flags and dune detecting it. I just don't know at which level we should add it (dune-project, package, stanza).

In the same way as we do for jsoo separate compilation.

[rgrinberg]

We discussed this in meeting today. The conclusion was that if you want to control this better, feel free to submit a PR to do so.