- Aug 08, 2016
-
-
Jacques-Henri Jourdan authored
-
Robbert Krebbers authored
This generalization is surprisingly easy in Iris 3.0, so I could not resist not doing it :).
-
Robbert Krebbers authored
This makes stuff more uniform and also removes the need for the [inGFs] type class. Instead, there is now a type class [subG Σ1 Σ2] which expresses that a list of functors [Σ1] is contained in [Σ2].
-
Robbert Krebbers authored
-
- Aug 06, 2016
-
-
Robbert Krebbers authored
-
- Aug 05, 2016
-
-
Robbert Krebbers authored
This better reflects the name of the bind rule. I renamed an internal tactic that was previously called wp_bind into wp_bind_core.
-
Robbert Krebbers authored
Use it to prove that tests/barrier_client and tests/heap_lang are adequate.
-
Robbert Krebbers authored
-
Robbert Krebbers authored
Also make those for introduction and elimination more symmetric: !% pure introduction % pure elimination !# always introduction # always elimination !> later introduction > pat timeless later elimination !==> view shift introduction ==> pat view shift elimination
-
Robbert Krebbers authored
This commit features: - A simpler model. The recursive domain equation no longer involves a triple containing invariants, physical state and ghost state, but just ghost state. Invariants and physical state are encoded using (higher-order) ghost state. - (Primitive) view shifts are formalized in the logic and all properties about it are proven in the logic instead of the model. Instead, the core logic features only a notion of raw view shifts which internalizing performing frame preserving updates. - A better behaved notion of mask changing view shifts. In particular, we no longer have side-conditions on transitivity of view shifts, and we have a rule for introduction of mask changing view shifts |={E1,E2}=> P with E2 ⊆ E1 which allows to postpone performing a view shift. - The weakest precondition connective is formalized in the logic using Banach's fixpoint. All properties about the connective are proven in the logic instead of directly in the model. - Adequacy is proven in the logic and uses a primitive form of adequacy for uPred that only involves raw views shifts and laters. Some remarks: - I have removed binary view shifts. I did not see a way to describe all rules of the new mask changing view shifts using those. - There is no longer the need for the notion of "frame shifting assertions" and these are thus removed. The rules for Hoare triples are thus also stated in terms of primitive view shifts. TODO: - Maybe rename primitive view shift into something more sensible - Figure out a way to deal with closed proofs (see the commented out stuff in tests/heap_lang and tests/barrier_client).
-
- Aug 04, 2016
-
-
Robbert Krebbers authored
It not behaves more consistently with iExact and thus also works in the case H : P -★ □^n Q |- Q.
-
Robbert Krebbers authored
-
- Aug 02, 2016
-
-
Robbert Krebbers authored
-
- Jul 28, 2016
-
- Jul 27, 2016
-
-
Robbert Krebbers authored
This way type class inference is not invokved when used in tactics like iPvs while not having to write an @. (Idea suggested by Ralf.)
-
Robbert Krebbers authored
This reverts commit 20b4ae55, which does not seem to work with Coq 8.5pl2 (I accidentally tested with 8.5pl1).
-
Robbert Krebbers authored
This makes type checking more directed, and somewhat more predictable. On the downside, it makes it impossible to declare the singleton on lists as an instance of SingletonM and the insert and alter operations on functions as instances of Alter and Insert. However, these were not used often anyway.
-
Ralf Jung authored
-
Robbert Krebbers authored
This way, it won't pick arbitrary (and possibly wrong!) inG instances when multiple ones are available. We achieve this by declaring: Hint Mode inG - - + So that type class inference only succeeds when the type of the ghost variable does not include any evars. This required me to make some minor changes throughout the whole development making some types explicit.
-
- Jul 21, 2016
-
-
Robbert Krebbers authored
In particular, remove ectx_language.atomic, because it seems unused expect for a smart constructor for language.atomic.
-
- Jul 20, 2016
-
-
Jacques-Henri Jourdan authored
* Values are considered as atomic expressions (this does not hurt, and this makes the proofs of atomicity simpler).
-
Robbert Krebbers authored
-
Robbert Krebbers authored
-
Robbert Krebbers authored
In order to improve flexibility, I have reverted the changes in commit 5cabd278 to counter, lock and spawn because an explicit namespace may be in the way of modularity, for example, if the interfaces of these libraries will expose namespaces through view shifts in the future. Exposure of namespaces in the case of par is very unlikely, so to that end, par remains to use an explicit namespace.
-
- Jul 19, 2016
-
-
Robbert Krebbers authored
-
Robbert Krebbers authored
-
Robbert Krebbers authored
-
Robbert Krebbers authored
-
Robbert Krebbers authored
-
Robbert Krebbers authored
-
Robbert Krebbers authored
I also reverted 7952bca4 since there is no need for atomic to be a boolean predicate anymore. Moreover, I introduced a hint database fsaV for solving side-conditions related to FSAs, in particular, side-conditions related to expressions being atomic.
-
Robbert Krebbers authored
-
Robbert Krebbers authored
-
Robbert Krebbers authored
-
Robbert Krebbers authored
We reify to a representation of expressions that includes an explicit constructor for closed terms. Substitution can then be implemented as the identify, which enables us to perform it using computation.
-
- Jul 18, 2016
-
-
Robbert Krebbers authored
-
Robbert Krebbers authored
-
Robbert Krebbers authored
-
- Jul 15, 2016
-
-
Robbert Krebbers authored
-
Robbert Krebbers authored
-