- Nov 24, 2016
-
-
Ralf Jung authored
-
- Nov 23, 2016
-
-
Robbert Krebbers authored
-
Robbert Krebbers authored
-
- Nov 22, 2016
- Nov 21, 2016
-
-
Robbert Krebbers authored
The old name didn't make much sense. Also now we can have pure_False too.
-
- Nov 20, 2016
-
-
Robbert Krebbers authored
-
- Nov 19, 2016
-
-
Robbert Krebbers authored
That range includes tabs and new lines. Thanks Morten for spotting this problem.
-
- Nov 10, 2016
-
-
Robbert Krebbers authored
This way we avoid the env_cbv tactic unfolding string related stuff that appears in the goal and hypotheses of the proof mode.
-
- Nov 03, 2016
-
-
Robbert Krebbers authored
-
Robbert Krebbers authored
The old choice for ★ was a arbitrary: the precedence of the ASCII asterisk * was fixed at a wrong level in Coq, so we had to pick another symbol. The ★ was a random choice from a unicode chart. The new symbol ∗ (as proposed by David Swasey) corresponds better to conventional practise and matches the symbol we use on paper.
-
- Nov 01, 2016
-
-
Robbert Krebbers authored
That's like what we are doing when instantiating an arrow or wand.
-
- Oct 28, 2016
-
-
Robbert Krebbers authored
This is more consistent with our current consensus of not using implication. Also, it allows one to reintroduce the persistent hypothesis into the spatial context.
-
Robbert Krebbers authored
-
- Oct 27, 2016
-
-
Robbert Krebbers authored
-
Robbert Krebbers authored
Since env_cbv does not unfold these apps, we should do it ourselves, to avoid ending up with partially evaluated terms.
-
- Oct 26, 2016
-
-
Robbert Krebbers authored
This fixes issue 39.
-
- Oct 25, 2016
-
-
Robbert Krebbers authored
-
Robbert Krebbers authored
-
Robbert Krebbers authored
There are now two proof mode tactics for dealing with modalities: - `iModIntro` : introduction of a modality - `iMod pm_trm as (x1 ... xn) "ipat"` : eliminate a modality The behavior of these tactics can be controlled by instances of the `IntroModal` and `ElimModal` type class. We have declared instances for later, except 0, basic updates and fancy updates. The tactic `iMod` is flexible enough that it can also eliminate an updates around a weakest pre, and so forth. The corresponding introduction patterns of these tactics are `!>` and `>`. These tactics replace the tactics `iUpdIntro`, `iUpd` and `iTimeless`. Source of backwards incompatability: the introduction pattern `!>` is used for introduction of arbitrary modalities. It used to introduce laters by stripping of a later of each hypotheses.
-
Robbert Krebbers authored
-
Robbert Krebbers authored
-
Robbert Krebbers authored
-
Robbert Krebbers authored
And also rename the corresponding proof mode tactics.
-
- Oct 13, 2016
-
-
Ralf Jung authored
-
- Oct 05, 2016
-
-
Robbert Krebbers authored
-
Robbert Krebbers authored
-
Robbert Krebbers authored
-
Robbert Krebbers authored
-
- Sep 28, 2016
-
-
Robbert Krebbers authored
-
Robbert Krebbers authored
-
- Sep 27, 2016
-
-
Robbert Krebbers authored
Used in iRevert, iClear, iFrame, and for generalizing the IH in iInduction and iLöb.
-
Robbert Krebbers authored
-
Robbert Krebbers authored
-
Robbert Krebbers authored
-
Robbert Krebbers authored
This way we can use uPred_valid for validity of uPreds, which more sense.
-
Robbert Krebbers authored
As proposed by JH Jourdan in issue 34.
-
- Sep 20, 2016
-
-
Robbert Krebbers authored
-
Robbert Krebbers authored
-
Robbert Krebbers authored
-