- Feb 24, 2016
-
-
Ralf Jung authored
-
Robbert Krebbers authored
This better seals off their definition. Although it did not give much of a speedup, I think it is conceptually nicer.
-
- Feb 23, 2016
-
-
Ralf Jung authored
-
Ralf Jung authored
-
Ralf Jung authored
-
Ralf Jung authored
-
Ralf Jung authored
-
Ralf Jung authored
-
Robbert Krebbers authored
I am now also using reification to obtain the indexes corresponding to the stuff we want to cancel instead of relying on matching using Ltac.
-
Robbert Krebbers authored
-
Robbert Krebbers authored
With Set Printing All, these notations make me loose overview entirely.
-
Ralf Jung authored
-
Ralf Jung authored
-
Ralf Jung authored
-
Robbert Krebbers authored
-
Ralf Jung authored
-
Ralf Jung authored
-
Ralf Jung authored
-
Ralf Jung authored
-
Ralf Jung authored
-
Ralf Jung authored
-
Ralf Jung authored
-
Ralf Jung authored
-
Ralf Jung authored
-
Ralf Jung authored
-
Ralf Jung authored
-
Ralf Jung authored
barrier: strive for consistency between barrierGF and the inGF assumptions; also change some instance names
-
Ralf Jung authored
-
Robbert Krebbers authored
-
- Feb 22, 2016
-
-
Robbert Krebbers authored
And now the part that I forgot to commit.
-
Robbert Krebbers authored
I made the list of iFunctors monomorphic to avoid having to deal with universe polymorphism, that is still somewhat flaky.
-
Robbert Krebbers authored
Also, give all these global functors the suffix GF to avoid shadowing such as we had with authF. And add some type annotations for clarity.
-
Robbert Krebbers authored
-
Robbert Krebbers authored
The non applied one should be only parsing.
-
Robbert Krebbers authored
due to an accidental git commit --amend after a git push.
-
Robbert Krebbers authored
-
Robbert Krebbers authored
In most cases there is a lot of duplicate proof search performed by both naive_solver and eauto. Especially since naive_solver calls its tactic (in the case of set_solver this used to be eauto) quite eagerly this made it very slow. Note that set_solver is this too slow and should be improved.
-
Robbert Krebbers authored
In most cases there is a lot of duplicate proof search performed by both naive_solver and eauto. Especially since naive_solver calls its tactic (in the case of set_solver this used to be eauto) quite eagerly this made it very slow. Note that set_solver is this too slow and should be improved.
-
Robbert Krebbers authored
-