th4s
th4s
> The issue with a trait like this is that it presumes that the number of communication rounds is constant. This is one of the reason we decided to ditch...
> I'm not totally convinced of the Setup/Execute abstraction, perhaps it is too high level? Yeah, I agree in some way. It is just an async function providing a channel....
Alright. Then no traits at the core level and different protocol traits on the aio level :+1:
Ack, makes sense for me.
What would be the correct approach to run them in parallel? I assume you have to spawn them as tasks, but this should probably be runtime-agnostic? What is the correct...
So by "mention how to run them in parallel" you mean I should just add the comment that one needs to invoke `spawn` on a runtime, or what do you...
Closing because outdated.
This will need to be adapted/rebased to the new architecture for IO.
Rebased and adapted to new IO design. Should be ready for review.
Rebased onto `threading-refactor`. Ready for review.