- Mar 05, 2017
-
-
Robbert Krebbers authored
-
Robbert Krebbers authored
-
Robbert Krebbers authored
-
Robbert Krebbers authored
-
- Feb 24, 2017
-
-
Robbert Krebbers authored
-
- Feb 22, 2017
-
-
Robbert Krebbers authored
-
- Feb 21, 2017
-
-
Robbert Krebbers authored
This fixes issue #72.
-
- Feb 15, 2017
-
-
Robbert Krebbers authored
-
Robbert Krebbers authored
-
- Feb 13, 2017
-
-
Jacques-Henri Jourdan authored
When using [iAssert ... with ">[]"], we should not use [tac_assert_persistent], and eliminate the modality instead. This patch is still not ideal, because some modalities (e.g., later) preserve persistence.
-
- Feb 12, 2017
-
-
Robbert Krebbers authored
For example, when having `"H" : ∀ x : Z, P x`, using `iSpecialize ("H" $! (0:nat))` now works. We do this by first resolving the `IntoForall` type class, and then instantiating the quantifier.
-
- Feb 11, 2017
-
-
Robbert Krebbers authored
-
Robbert Krebbers authored
Instead of doing all the instantiations by invoking a single type class search, it now performs the instantiations by invoking individual type class searches. This a.) gives better error messages and b.) works when `xj` depends on `xi`.
-
Robbert Krebbers authored
In the following ways: - When having `P → Q` it will now also work when the spatial context is non-empty. - When having `∀ x : A, Q` it will now do an `iIntros (_)`.
-
- Feb 09, 2017
-
-
Robbert Krebbers authored
In this case, we cannot use all the hypotheses for proving the premises as well as for the remaining goal.
-
Robbert Krebbers authored
-
- Feb 06, 2017
-
-
Ralf Jung authored
-
- Jan 30, 2017
-
-
Robbert Krebbers authored
This fixes issue #57. I considered supporting these introduction patterns also in a nested fashion -- for example allowing `iDestruct foo as [H1 [{H1} H1 /= H2|H2]` -- but that turned out to be quite difficult. Where should we allow `/=`, `{H}` and `{$H}` exactly. Clearly something like `>/=` makes no sense, unless we adopt to some kind of 'stack like' semantics for introduction patterns as in ssreflect. Alternatively, we could only allow these patterns in the branches of the destructing introduction pattern `[... | ... | ...]` but that brings other complications, e.g.: - What to do with `(H1 & /= & H3)`? - How to distinguish the introduction patterns `[H _]` and `[_ H]` for destructing a spatial conjunction? We cannot simply match on the shape of the introduction pattern anymore, because one could also write `[_ H /=]`.
-
Robbert Krebbers authored
-
Robbert Krebbers authored
-
- Jan 29, 2017
-
-
Robbert Krebbers authored
-
- Jan 24, 2017
-
-
Robbert Krebbers authored
This fixes issue #67.
-
Robbert Krebbers authored
-
Robbert Krebbers authored
It now copies the hypothesis when: 1.) it is persistent 2.) when destructing it requires a universal quantifier to be instantiated. The new behavior is implemented using a type class (called CopyDestruct) so that it can easily be extended.
-
Robbert Krebbers authored
-
- Jan 23, 2017
-
-
Robbert Krebbers authored
-
Robbert Krebbers authored
-
- Jan 22, 2017
-
-
Robbert Krebbers authored
This fixes issue #51.
-
Robbert Krebbers authored
This fixes issue #62.
-
- Jan 20, 2017
-
-
Robbert Krebbers authored
The error message accidentally got removed in e0789039.
-
Robbert Krebbers authored
-
- Jan 12, 2017
-
-
Robbert Krebbers authored
-
- Jan 11, 2017
-
-
Robbert Krebbers authored
-
- Jan 05, 2017
-
-
Ralf Jung authored
-
Robbert Krebbers authored
-
- Jan 04, 2017
-
-
Robbert Krebbers authored
This fixes issue #61.
-
- Jan 03, 2017
-
-
Ralf Jung authored
This patch was created using find -name *.v | xargs -L 1 awk -i inplace '{from = 0} /^From/{ from = 1; ever_from = 1} { if (from == 0 && seen == 0 && ever_from == 1) { print "Set Default Proof Using \"Type*\"."; seen = 1 } }1 ' and some minor manual editing
-
- Jan 01, 2017
-
-
Robbert Krebbers authored
For iApply and iRewrite we want that, but for iDestruct and iMod we do not. This fixes issue #52.
-
- Dec 28, 2016
-
-
Robbert Krebbers authored
-
- Dec 27, 2016
-
-
Robbert Krebbers authored
-