Conversation
41732e9 to
b5fc08c
Compare
|
A lot of values there are for coq_makefile and will go away at some point to a coq-makefile specific tool. We should not include them. |
|
Let's choose which ones then. I propose the following, you can edit as you see fit:
The rest might be useless, but it is harmless to read them when they are available today. Even if they get removed in the future, it will allow Dune to understand configuration of Coq from previous versions etc. |
|
Only two useful for us are coqlib and native compiler. |
|
@ejgallego We have access to all of them under the hood, so for "us" this doesn't matter. I'm talking about exposing them to the user, and I think something like |
Signed-off-by: Ali Caglayan <alizter@gmail.com> ps-id: fcb7d085-dc87-45a7-a37b-75ad0cd535c5 Signed-off-by: Ali Caglayan <alizter@gmail.com>
b5fc08c to
9f0e5e1
Compare
|
I think that being conservative on what we expose will avoid any future problems. Why would Actually, while we need ourselves access to these variables to implement a few features, why would a user ever need access to these variables? Do we have use cases? |
|
OK I will restrict the available variables. |
We add an interface for the configuration values of Coq. This is important as it allows us to have version specific code. As a secondary we can expose it to users in their stanzas. We might want to cut down on the number however.
This adds a new
%{coq:...}macro which lets you read the following:The output of
coqc --config:Version numbers for Coq:
TODO: