Thomas Eizinger
Thomas Eizinger
To progress on this front (other than something like #2878), I am thinking of going with a `FuturesUnordered` wrapper that: - Wraps the future in a timeout - Never returns...
> While this is a nice simplification, I am not sure if it is necessarily a good idea. It is a little less clear exactly what features are enabled and...
> > Happy to change it back but I also like the simplicity of not needing to set features. I do see though how it can trigger the thought of...
Resolved! Sorry for the delay.
Resolved in #192.
I am guessing the major speed difference comes from the allocations. `xtra` performs at least two allocations as part of wrapping messages in its envelope, plus there might be allocations...
> True - this is simply the cost you pay for dynamic message dispatch. I would wonder how it'd look if the Tokio example also dynamically dispatched message handlers Would...
> > Would that be a fair comparison though? The actor as shown in the benchmark is how I'd implement it. With an enum to handle multiple cases. > >...
> Is it not the case that if the user wants to poll another future during the loop of an actor, a single, combined receive-and-tick would prevent this? I am...
I put up a PR here: #194.