- Mar 16, 2020
-
-
- remove "odd" comment - move atomic triples to bi_scope
-
- Mar 12, 2020
-
-
Robbert Krebbers authored
-
- Mar 10, 2020
-
-
Robbert Krebbers authored
-
- Feb 28, 2020
-
-
Ralf Jung authored
-
- Feb 23, 2020
-
-
-
Tej Chajed authored
-
- Feb 18, 2020
-
-
Robbert Krebbers authored
-
Robbert Krebbers authored
-
Ralf Jung authored
-
Ralf Jung authored
-
- Feb 11, 2020
- Feb 10, 2020
-
-
Robbert Krebbers authored
-
Robbert Krebbers authored
-
- Feb 01, 2020
-
-
Robbert Krebbers authored
-
- Jan 15, 2020
-
-
Robbert Krebbers authored
-
- Jan 13, 2020
-
-
Robbert Krebbers authored
-
- Jan 09, 2020
-
-
Ralf Jung authored
-
- Jan 08, 2020
- Dec 13, 2019
-
-
Maxime Dénès authored
-
- Dec 06, 2019
-
-
Ralf Jung authored
-
- Nov 22, 2019
-
-
When proving `foo` through a fixpoint, Coq's guardedness checker needs to see to which arguments `foo` is applied. Opaque lemmas applied to `foo` itself prevent that, so make them transparent. * Make `IntoEmpValid` lemmas transparent. * Expose application of `IntoEmpValid` instance to its argument. * Add comment to `tac_pose_proof` This MR brings back the type of `tac_pose_proof` to the one it had before !329. Hence, this seems worth a comment.
-
- Nov 20, 2019
-
-
Robbert Krebbers authored
This test case arose in Iron.
-
Robbert Krebbers authored
Also, rewrite `iIntoEmpValid`. Now, instead of using Ltac to traverse the type of the term and generate goals for the premises, we repeatedly apply a series of lemmas. This has the advantage that it works up to convertability, and we no longer need the `eval ...` hacks.
-
- Nov 10, 2019
-
-
Robbert Krebbers authored
Fix issue pointed out by @tchajed in !330 (comment 41322)
-
- Nov 08, 2019
-
-
Paolo G. Giarrusso authored
-
Paolo G. Giarrusso authored
-
Paolo G. Giarrusso authored
-
- Nov 07, 2019
-
-
Robbert Krebbers authored
-
- Nov 05, 2019
-
-
Robbert Krebbers authored
-
- Oct 09, 2019
-
-
Ralf Jung authored
-
- Sep 20, 2019
-
-
Ralf Jung authored
-
- Sep 19, 2019
-
-
Robbert Krebbers authored
-
Robbert Krebbers authored
-
Robbert Krebbers authored
-
- Sep 13, 2019
-
-
Jacques-Henri Jourdan authored
The general idea is to first import/export modules which are further than the current one, and then import/export modules which are close dependencies. This commit tries to use the same order of imports for every file, and describes the convention in ProofGuide.md. There is one exception, where we do not follow said convention: in program_logic/weakestpre.v, using that order would break printing of texan triples (??).
-
- Sep 08, 2019
-
-
Jacques-Henri Jourdan authored
-
Jacques-Henri Jourdan authored
-
- Aug 14, 2019
-
-
Ralf Jung authored
-