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.
then the transition function will have access to v (Ref1, Ref2) rather than the much more useful (v Ref1, v Ref2).
Not sure how to solve this. It would be nice if failing semantics, i.e. when transition has access to Either err (v Ref) could also be made a special case of the solution.
The text was updated successfully, but these errors were encountered:
This complicates the definition of actions however, by indexing them by Response rather than just *... It's also not as general as it could be, i.e. lets say you want to return three references. One could imagine using , data Response = ... | Response :*: Response instead, but this would make the implementation of, say, generating programs tricker (where we would need to use Typeable or singletons to reify the response and do the appropriate thing).
I guess another approach is to drop the indexing of actions altogether as discussed in #170. Something like:
dataResponse'vresperr=Return (vresp)
| err :+: v resp
| v resp :*: v resp
typeTransition'modelactresperr=forallv.modelv->actv->Response'vresperr->modelv
If we have an action like:
then the transition function will have access to
v (Ref1, Ref2)
rather than the much more useful(v Ref1, v Ref2)
.Not sure how to solve this. It would be nice if failing semantics, i.e. when transition has access to
Either err (v Ref)
could also be made a special case of the solution.The text was updated successfully, but these errors were encountered: