GitLab

New atomic updates: defined as a fixed point with existential quantifier; intro lemma using class of Laterable assertions

There's a very low risk of these conflicting with Coq's standard library

New IntoAcc typeclass to decouple creating and elliminating accessors; ElimInv supports both with and without Hclose

Extend ElimModal with Boolean flags to specify whether it operates on the persistent/spatial context.

This is backwards-compatible; it desugars to a normal application on previous versions

This requires changing the Hint Mode of the [Frame] type class because it should not fail if its parameter is an evar, but instantiate it instead. In order to prevent all the other instances of [Frame] to intantiate this evar themselves, we create a new type class [KnwonFrame], which corresponds to the old behavior.

This supports Iris 2 like update modalities, as used in e.g. by @jtassaro.

This commit fixes issue #154.

We already used the following naming convention: `wp_value'` is stated in
terms of `of_val` and `wp_value` is stated in terms of `IntoVal`. This
commit applies this convention to `wp_value_inv` as well.

This used to be done by using `ElimModal` in backwards direction. Having
a separate type class for this gets rid of some hacks:

- Both `Hint Mode`s in forward and backwards direction for `ElimModal`.
- Weird type class precedence hacks to make sure the right instance is picked.
  These were needed because using `ElimModal` in backwards direction caused
  ambiguity.