This assert was likely inherited from some point, but it's not quite valid as a no-timeout read may enter this loop, but data could be stolen by any other read after the socket is deemed readable. I saw this fail in a recent bors run where the assertion was tripped. |
||
|---|---|---|
| .. | ||
| io | ||
| lib.rs | ||
| task.rs | ||