Re:Futurelock: A subtle risk in async Rust
by grogers on Friday October 31, 2025 @08:38PM
(#45778241)
I'm not familiar with tokio, but I am familiar with folly coro in C++ which is similiar-ish. You cannot co_await a folly::coro::Task by reference, you must move it. It seems like that prevents this bug. So maybe select! is the low level API and a higher level (i.e. safer) abstraction can be built on top?
[ Parent
| on HN ]
There are no comments on this comment yet.