> I am not happy that the futures I painfully walked over hot coals to make work will be easily replaced by async/await
Glad I'm not the only one who was struggling with gigantic and confusing error messages that were fixed by trial and error (usually adding a `.map_err(|_| ())`).
Re:Rust 2018 survey results
by continuations on Tuesday November 27, 2018 @07:54PM
(#18548347)
> With actix-web, you can run asyncio and sync code in the same server. It lets you take full advantage of Rust's concurrency.
Will actix-web become obsolete or be replaced when Rust releases async/await in 2019?
Re:Rust 2018 survey results
by steveklabnik on Tuesday November 27, 2018 @08:19PM
(#18548466)
No; async/await produces Futures, which is what actix-web uses.
It will use a slightly older futures, but that's why there's a compatibility layer, and I'm sure they'll update fairly quickly after stabilization and so you could just use that version as well.
If anyone likes to compare apples with oranges and benchmarking web frameworks, actix-web framework (optimised for benchmarking, naturally) is leading in many categories: https://www.techempower.com/benchmarks/#section=data-r17&hw=...
With actix-web, you can run asyncio and sync code in the same server. It lets you take full advantage of Rust's concurrency.