- 27 Mar, 2018 1 commit
-
-
Robbert Krebbers authored
-
- 06 Mar, 2018 1 commit
-
-
Robbert Krebbers authored
-
- 29 Nov, 2017 1 commit
-
-
Robbert Krebbers authored
-
- 12 Nov, 2017 1 commit
-
-
Robbert Krebbers authored
This follows the associativity in Haskell. So, something like f <$> g <$> h Is now parsed as: (f <$> g) <$> h Since the functor is a generalized form of function application, this also now also corresponds with the associativity of function application, which is also left associative.
-
- 09 Nov, 2017 1 commit
-
-
Robbert Krebbers authored
-
- 28 Oct, 2017 1 commit
-
-
Robbert Krebbers authored
This way, we will be compabile with Iris's heap_lang, which puts ;; at level 100.
-
- 27 Oct, 2017 1 commit
-
-
Jacques-Henri Jourdan authored
-
- 06 Oct, 2017 1 commit
-
-
Hai Dang authored
-
- 29 Sep, 2017 3 commits
-
-
Robbert Krebbers authored
-
Robbert Krebbers authored
This fixes the issue of Hai in !6.
-
Hai Dang authored
-
- 21 Sep, 2017 1 commit
-
-
Robbert Krebbers authored
This allows for more control over `Hint Mode`.
-
- 17 Sep, 2017 1 commit
-
-
Robbert Krebbers authored
This provides significant robustness against looping type class search. As a consequence, at many places throughout the library we had to add additional typing information to lemmas. This was to be expected, since most of the old lemmas were ambiguous. For example: Section fin_collection. Context `{FinCollection A C}. size_singleton (x : A) : size {[ x ]} = 1. In this case, the lemma does not tell us which `FinCollection` with elements `A` we are talking about. So, `{[ x ]}` could not only refer to the singleton operation of the `FinCollection A C` in the section, but also to any other `FinCollection` in the development. To make this lemma unambigious, it should be written as: Lemma size_singleton (x : A) : size ({[ x ]} : C) = 1. In similar spirit, lemmas like the one below were also ambiguous: Lemma lookup_alter_None {A} (f : A → A) m i j : alter f i m !! j = None
↔ m !! j = None. It is not clear which finite map implementation we are talking about. To make this lemma unambigious, it should be written as: Lemma lookup_alter_None {A} (f : A → A) (m : M A) i j : alter f i m !! j = None↔ m !! j = None. That is, we have to specify the type of `m`.
-
- 06 Sep, 2017 3 commits
-
-
Robbert Krebbers authored
-
Robbert Krebbers authored
-
Dan Frumin authored
-
- 26 Jun, 2017 1 commit
-
-
Robbert Krebbers authored
-
- 30 May, 2017 1 commit
-
-
Dan Frumin authored
-
- 25 May, 2017 5 commits
-
-
Robbert Krebbers authored
-
Robbert Krebbers authored
-
Robbert Krebbers authored
-
Robbert Krebbers authored
-
Robbert Krebbers authored
-
- 15 Mar, 2017 1 commit
-
-
Robbert Krebbers authored
-
- 09 Mar, 2017 1 commit
-
-
Robbert Krebbers authored
To be consistent with Iris, see Iris commit 9ee62b3a.
-
- 16 Feb, 2017 1 commit
-
-
Robbert Krebbers authored
-
- 07 Feb, 2017 1 commit
-
-
Robbert Krebbers authored
-
- 31 Jan, 2017 8 commits
-
-
Robbert Krebbers authored
This fixes issue #65.
-
Robbert Krebbers authored
-
Robbert Krebbers authored
-
Robbert Krebbers authored
Rename: - prefix_of -> prefix and suffix_of -> suffix because that saves keystrokes in lemma names. However, keep the infix notations with l1 `prefix_of` l2 and l1 `suffix_of` l2 because those are easier to read. - change the notation l1 `sublist` l2 into l1 `sublist_of` l2 to be consistent. - rename contains -> submseteq and use the notation ⊆+
-
Robbert Krebbers authored
-
Ralf Jung authored
-
Ralf Jung authored
-
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
-
- 09 Dec, 2016 1 commit
-
-
Ralf Jung authored
-
- 15 Nov, 2016 1 commit
-
-
Robbert Krebbers authored
-
- 28 Sep, 2016 1 commit
-
-
Robbert Krebbers authored
-
- 27 Sep, 2016 2 commits
-
-
Robbert Krebbers authored
-
Robbert Krebbers authored
-