Repository navigation
concurrency: re-export futures-concurrency? #17
Description
We believe tasks are the wrong abstaction. Lets instead make it as easy as possible for wstd users to use the right abstraction by re-exporting futures-concurrency, @yoshuawuyts 's crate that provides the right abstraction, and use it in wstd's examples and docs.
Activity
pchickey commentedon Nov 19, 2024
Right now the thinking is we will re-export all of the modules from
futures-concurrencyexcept forprelude, and define apub mod prelude { pub use futures_concurrency::prelude::*; pub use crate::io::{AsyncRead, AsyncWrite}, etc etc }pchickey commentedon Sep 24, 2025
We added tasks in #86.
teohhanhui commentedon Sep 24, 2025
Has this changed?
pchickey commentedon Sep 24, 2025
At least personally I'd change my feelings to "tasks are the abstraction of last resort" rather than always wrong, but the broader ecosystem more or less demands tasks, and component model async has tasks. So, we relented.
yoshuawuyts commentedon Sep 25, 2025
To expand on this: we want to be able to support Axum and Hyper on
wstd, and both of these assume a particular task model. While I still hold that the tasks model is wrong, creating practical software now is more important than ideological purity.