The Future Trait Has A Missing State
0 comments · rust
- Comments8
0 comments · rust
Story details from Lobsters ↗ · linked article on blog.yoshuawuyts.com.
The Future Trait Has A Missing State was first seen on Lobsters · Hottest on Oct 29, 2026. Since then it has appeared in 64 checks on 3 different days. Its best position was #8 of 25, reached on Oct 29, 14:49 UTC. It dropped off the list after Nov 1, 17:21 UTC.
Position on Lobsters · Hottest at every check (lower is better).
Best rank per day (UTC).
Platform metric as reported by Lobsters.
A few top-level comments from Lobsters, shortened. Read the full thread on Lobsters.
I don't really understand the problem here, and I think panicking when you attempt to poll a future after it has already completed is a fine behaviour. To me, the behaviour of `Fuse::poll` when called on a terminated future is a smell akin to handling EBADF from syscalls. It too should panic because doing so…
> However this unfortunately abuses `Poll::Pending`, whose docs state: "When a function returns `Pending`, the function must also ensure that the current task is scheduled to be awoken when progress can be made." This definition is incompatible with how `Fuse` uses `Pending`, and so bringing it into the stdlib would…
The author clearly has expertise here which I will defer to, but I'm not sure I understand this argument. It seems like under what they are proposing, every future would be internalizing the business logic of `MaybeDone`? But then there is the possibility that this business logic is implemented incorrectly. Is that…
Archived daily, weekly and monthly lists that include this entry.
Not at the moment. It was last on the list on Nov 1, 17:21 UTC, after 3 days of trending.
#8 on Lobsters · Hottest, on Oct 29, 14:49 UTC. Trendoday checks this list every 30 minutes.
It was first seen on Oct 29, 2026 and has been on the list on 3 days (64 checks) since.