eclipse-zenoh-flow
[Enhancement] Should `async_std` be replaced with `tokio` ?
Current behaviour and limitations
Since #261, Zenoh-Flow has been based on Zenoh 1.x. A major change in this version of Zenoh is that task management has shifted from async_std to tokio (https://github.com/eclipse-zenoh/zenoh/pull/1264).
Should Zenoh-Flow migrate entirely to tokio?
Proposed solution?
No response
Hi @Hennzau!
In short, yes we should probably switch to Tokio.
The longer answer is that we had internal plans to use a patched version of async-std to provide additional functionalities. For instance, assigning a priority to a task. Unfortunately, due to external factors, these plans are now postponed and to have a more consistent software stack between the Zenoh and Zenoh-Flow projects, Tokio is the better default.
Alright! Yes, I remember M. Angelo C mentioning this version of async_std.
I’ll update the code to use tokio!