3 ms·
I have experienced this without any need for async. This is just lack of standardization. Same story can happen with time/decimals/database drivers. However p
by Ygg2 4y ago
I have experienced this without any need for async. This is just lack of standardization.
Same story can happen with time/decimals/database drivers.
However pulling it into std would probably kill the library because backwards compatibility guarantees.
- sanxiyn 4y agoTokio is 1.0 since 2020 and they declared to maintain backwards compatibility for a minimum of 5 years. Tokio already made backwards compatibility guarantees and it hasn't been killed so far.
- carllerche 4y agoIt isn't a question of backwards compatibility, it is just way easier to iterate / evolve in a crate than it is in stdlib. For example, Tokio has the concept of "unstable" features, which have stronger stability guarantees than Rust nightly. First, you can use them with the stable rust compiler, second we guarantee that unstable features will not break across patch releases. This may seem small, but it lets us experiment with new functionality and get real world usage. Many of our users cannot use Rust nightly but can use Tokio unstable features.
- Ygg2 4y agoYeah carlleche nailed it. `std` is where libs go to die in Python sense. I didn't imply anything about Tokio. I just wish some libs didn't need to be bikeshedded (like async runtime, time, decimal, etc.)