Re:How Rust optimizes async/await
by GolDDranks on Monday August 19, 2019 @11:57PM
(#20743717)
Note that this applies only to tasks that are !Sync. If they aren't, two tasks accessing the same state could be moved to different threads and access that state racily. In that case .await tells you nothing about accessing non-local state. However, for purposefully single-threaded task pools avoiding locks this way certainly seems possible.
[ Parent
| on HN ]
There are no comments on this comment yet.