snaggen@programming.dev to Rust@programming.devEnglish · 1 year agoThe State of Async Rust: Runtimescorrode.devexternal-linkmessage-square7fedilinkarrow-up145arrow-down11cross-posted to: rust@lemmy.ml
arrow-up144arrow-down1external-linkThe State of Async Rust: Runtimescorrode.devsnaggen@programming.dev to Rust@programming.devEnglish · 1 year agomessage-square7fedilinkcross-posted to: rust@lemmy.ml
minus-squared_k_bo@feddit.delinkfedilinkarrow-up1·1 year ago In fact, I would hypothesize that, from an ecosystem adoption POV, tokio’s only killer feature is hyper’s dependence on it. AFAICT, the current hyper v1 release candidate only depends on tokio for tokio::sync::{mpsc, oneshot} (and sync is the only enabled feature). It’s intended to be runtime-agnostic. See also https://docs.rs/hyper/1.0.0-rc.4/hyper/rt/trait.Executor.html . I agree that its ecosystem is still very tokio-centric.
AFAICT, the current hyper v1 release candidate only depends on tokio for
tokio::sync::{mpsc, oneshot}(andsyncis the only enabled feature).It’s intended to be runtime-agnostic. See also https://docs.rs/hyper/1.0.0-rc.4/hyper/rt/trait.Executor.html . I agree that its ecosystem is still very tokio-centric.