News for hackers. Stuff that matters.

A comment on Comparison of Rust async and Linux thread context switch time and memory use. Parent comment

Re:Comparison of Rust async and Linux thread context switch ... by littlestymaar on Friday February 12, 2021 @05:50AM (#26112293)
In Javascript, this is a typical rookie mistake. Every newcomer would do it once, get lectured about `Promise.all` in code review, and move on.

Honestly, I'd be really surprised if this was a common practice in C#.

[ Parent | on HN ]
Re:Comparison of Rust async and Linux thread context switch ... by baby on Friday February 12, 2021 @06:16AM (#26112444)
Rust doesn’t allow you to do this.
[ Parent | on HN ]
Re:Comparison of Rust async and Linux thread context switch ... by littlestymaar on Friday February 12, 2021 @06:40AM (#26112612)
What makes you think so?

From a quick ddg search, it looks it does: https://docs.rs/futures/0.3.8/futures/macro.join.html

[ Parent | on HN ]
Re:Comparison of Rust async and Linux thread context switch ... by imtringued on Friday February 12, 2021 @08:42AM (#26113527)
All you have to do is wrap multiple futures into a single one and then await on the combined one. There is no programming language on earth that can prevent this.
[ Parent | on HN ]