You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
stateAssert is currently used within the design spec to assert properties about the state. However, given that we do not translate the string associated with the Haskell assert into the design spec, our use of stateAssert offers no benefit over state_assert.
We should investigate replacing stateAssert with state_assert, which would require a change to the Haskell translator.
Alternatives include
having a global simp that turns stateAssert into state_assert and rewriting our corres_underlying/ccorres_underlying rules in terms of state_assert, or
providing lemmas statements for our existing corres_underlying/ccorres_underlying rules to use state_assert instead of stateAssert, for example ccorres_stateAssert[simplified stateAssert_def] or similar
The text was updated successfully, but these errors were encountered:
stateAssert
is currently used within the design spec to assert properties about the state. However, given that we do not translate the string associated with the Haskellassert
into the design spec, our use ofstateAssert
offers no benefit overstate_assert
.We should investigate replacing
stateAssert
withstate_assert
, which would require a change to the Haskell translator.Alternatives include
having a global
simp
that turnsstateAssert
intostate_assert
and rewriting ourcorres_underlying/ccorres_underlying
rules in terms ofstate_assert
, orproviding
lemmas
statements for our existingcorres_underlying/ccorres_underlying
rules to usestate_assert
instead ofstateAssert
, for exampleccorres_stateAssert[simplified stateAssert_def]
or similarThe text was updated successfully, but these errors were encountered: