3 ms·
tokio itself is not mature/stable enough to be in the standard library, IMO, let alone anything based on tokio.
by bryanlarsen 2y ago
tokio itself is not mature/stable enough to be in the standard library, IMO, let alone anything based on tokio.
- rsanders 2y agoI'm pretty new to Rust so forgive me if I'm mistaken, but it seems to me that this crate doesn't require the use of tokio.
- lesuorac 2y agoWhen all the examples are marked with `#[tokio::main]`, it probably requires tokio. Although I guess they do implement Future on their own so it shouldn't need a specific runtime then. https://github.com/fortress-build/whirlwind/blob/main/src/shard/futures.rs https://github.com/fortress-build/whirlwind/blob/main/src/sh...
- blurbleblurble 2y agoThey're just using tokio as a dev dependency. You could use this with any async runtime https://github.com/fortress-build/whirlwind/blob/main/Cargo.toml#L14 https://github.com/fortress-build/whirlwind/blob/main/Cargo....
- willothy 2y agoTokio is just used for async tests and the examples, the crate doesn’t depend on any specific async runtime :)