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
{{ message }}
This repository has been archived by the owner on Jun 18, 2021. It is now read-only.
We have an instance (Eq1 v, Eq a) => Eq (Reference v a) , which requires that the underlying reference type be comparable (Eq a). That happens to be fine with IORef but in general reference types such as mutable vectors do not have such an instance. A workaround is a wrapper that carries a unique identifier for each reference (see here for example), but could qc-state-machine integrate that somehow?
The text was updated successfully, but these errors were encountered:
I thought a bit more about this, and I'm beginning to wonder if post-conditions shouldn't have the type model Symbolic -> act Symbolic resp -> resp -> Bool?
Or perhaps the Var from Symbolic can be threaded through into Concrete and used for equality checks?
We have an instance
(Eq1 v, Eq a) => Eq (Reference v a)
, which requires that the underlying reference type be comparable (Eq a
). That happens to be fine withIORef
but in general reference types such as mutable vectors do not have such an instance. A workaround is a wrapper that carries a unique identifier for each reference (see here for example), but could qc-state-machine integrate that somehow?The text was updated successfully, but these errors were encountered: