-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
replace fsdist_convA by its generic version convA0 #122
Conversation
I don't get the CI failures, it works on my computer. What about yours? |
It compiles on my machine with coq-8.17.0, mathcomp-1.17.0, analysis-0.6.3, infotheo-0.5.2. |
Type <= Type being a missing universe constraint looks very weird |
I guess that's because we do not see the indices but I can't reproduce on my machine (Coq 8.16.1, MathComp 1.16.0, analysis 0.6.1, infotheo 0.5.1) |
let me temporarily Set Printing All just before the erroneous Equations line |
HB is broken? My local HB is 1.4.0 and the CI is using 1.6.0. |
Oh! That is likely to be of interest to HB developers indeed. |
Confirmed locally that it fails with coq-8.17.1, elpi-1.18.0, and HB-1.6.0. elpi versions may matter; I have just noticed elpi-1.17.1 + HB-1.6.0 fails to compile mathcomp-classical-0.6.4 while elpi-1.18 + HB-1.6.0 succeeds. |
The same error with coq-8.18.0 + elpi-1.19.0 + HB-1.6.0. |
I'm a bit lost with versions.
I believe Coq-Elpi 1.18 and 1.19 are very similar w.r.t. universes. The message above is unclear to me, is 1.18 working or not? Can you help me reproduce the problem? It seems to me that Equations does not add a constraint, and that maybe the constraint was previously added by Coq-Elpi, possibly hiding the bug (and maybe the constraint is not needed per se in the term synthesized by Coq-Elpi/HB). One way to tell would be to give by hand the term generated by Equations, and see if the bug is still there. If I'm right, one could alternatively add by hand the missing constraint between u0 and the universe of tuples (by adding a dummy definition before the call to equations, a definition that forces that constraint) to work around the bug. |
HB 1.4.0 succeeds to compile monae master and HB-1.6.0 fails, regardless of the versions of elpi used. HB 1.6.0 + elpi 1.18 succeeds to compile mathcomp-analysis 0.6.4 and HB 1.6.0 + elpi 1.17.1 fails. I'll try your suggestion to feed a term directly. |
Oh I have just noticed coq-elpi and elpi are different packages. The versions so far I wrote about elpi was of coq-elpi. |
That is fine, |
If I'm right, then adding/removing a call to the type checker (in coq-elpi or HB) is sufficient to trigger/avoid a bug in equations. If you have all version around, then checking if/when the constraint between the u0 (or |
We realized that there is another issue that affects MathComp-Analysis: coq-elpi 1.18 + HB 1.5.0 -> analysis compiles |
However, that still leaves the issue with monae: |
I plan to put monae in nixpkgs so that it can go to the nixconfig of HB but this will take some time |
Just an update about Monae and Hierarchy-builder. So in the end I didn't complete the bisect between HB 1.5.0 and 1.6.0 I promised. Let us add that we are really happy with HB: we managed to use it to add another, fairly complicated monad |
b192817
to
990815d
Compare
@t6s I have rebased this branch on master. |
LGTM |
Then I release. |
proba_monad_model.v uses another form of convA that is also specific to fsdist: fsdist_convA.
This PR replaces it by its generic version convA0.
I intend to remove fsdist_convA from infotheo as its only use seems to be here.