3 ms·
There is quite some support for the second option. But it is not advertised at all. E.g. there is an entire local task pool impl in tokio_util, but it is not e
by rklaehn 3y ago
There is quite some support for the second option. But it is not advertised at all.
E.g. there is an entire local task pool impl in tokio_util, but it is not enabled by default and at least for me was difficult to find. https://docs.rs/tokio-util/latest/tokio_util/task/struct.LocalPoolHandle.html# https://docs.rs/tokio-util/latest/tokio_util/task/struct.Loc...
I wrote an entire local executor pool before finding that thing and ripping my code out again...
At the very least the support for tasks for non-Send futures should be advertized more, and maybe also the APIs polished a bit.
- yencabulator 3y agoAnd yet glommio exists separately from tokio, because apparently it couldn't be achieved using tokio. https://www.datadoghq.com/blog/engineering/introducing-glommio/ https://www.datadoghq.com/blog/engineering/introducing-glomm... I am eager to see what comes of tokio-uring, though. Especially if someone comes up with a good API for reads using shared buffer pools... that one might cause API changes everywhere.