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 GordonS on Friday February 12, 2021 @09:53AM (#26114232)
Maybe if you spray threads around at random :), but in real-world use I find it much easier to pinpoint where the problem occurred, and the path taken to get there. Also, at least with threads you can get the thread ID and/or name.

Regarding shared, mutable state - if multiple async "threads" can access that state, then you still need to guard it, but usually with an async-capable means.

[ Parent | on HN ]
Re:Comparison of Rust async and Linux thread context switch ... by littlestymaar on Friday February 12, 2021 @01:44PM (#26116976)
> Regarding shared, mutable state - if multiple async "threads" can access that state, then you still need to guard it, but usually with an async-capable means.

Sometimes, but not as often, because the scope of your async function is often the only “shared state” you need.

[ Parent | on HN ]