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
The current implementations of fanout and fanin are purely sequential; they're basically just for-loops for parties. This means that, in the common situation where everyone is broadcasting to everyone, the party N won't send anything until they've received N-1 messages from peers. Fix this using concurrency somehow.
(This is going to require doing something clever with the way messages are handled, because concurrent choreographies will break the current system.)
The text was updated successfully, but these errors were encountered:
The current implementations of fanout and fanin are purely sequential; they're basically just for-loops for parties. This means that, in the common situation where everyone is broadcasting to everyone, the party N won't send anything until they've received N-1 messages from peers. Fix this using concurrency somehow.
(This is going to require doing something clever with the way messages are handled, because concurrent choreographies will break the current system.)
The text was updated successfully, but these errors were encountered: