Restioson

I think that's a good solution, thanks :)

Thanks for adding the comment! Can be merged after conflicts are resolved

Good catch! This was probably missed in #102. Feel free to open a PR, I'd appreciate that :)

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 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. It's comparing different...

> As a user though, I don't really care what xtra is using internally? I think xtra is quite appealing from an ergonomics perspective. The only thing that these benchmarks...

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?

Could you give an example on how an API for this could look?

Notes toward documentation on this topic: ## Send - If `SendFut` is called but never polled, the item is not sent. - If `SendFut` is polled and returns `Poll::Pending`, it...

> Does this mean that if SendFut is polled at least once and it returns Pending and then never polled again, the message might still be sent? Yes, indeed. The...