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
In various contexts, including some of our (planned) examples, we care about the transcripts (views) of various parties. We should write handlers to gather them explicitly.
The text was updated successfully, but these errors were encountered:
--| Each location is associated with a message buffer which stores messages sent-- from other locations.typeMsgBuf=HashMapLocTm (ChanString)
newtypeLocalConfig=LocalConfig{locToBuf::HashMapLocTmMsgBuf}
No, I don't think so. It's using Chans, which "store" the messages only until the relevant process consumes them.
I'm sure we could shim this to do what we want, and I'm not opposed to that, but it'd be smelly. We shouldn't need concurrency for this; something that works like Choreography.Choreo.runChoreo, but with the side-effect of accumulating everyone's views as state, would seem like the "right" way to do it.
In various contexts, including some of our (planned) examples, we care about the transcripts (views) of various parties. We should write handlers to gather them explicitly.
The text was updated successfully, but these errors were encountered: