haven't processed the messages at that point.Can we just post a task to quit the run loop, or do we really need to ensure the run loop is empty and not just "all tasks before this quit closure was posted have run"?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
haven't processed the messages at that point.Can we just post a task to quit the run loop, or do we really need to ensure the run loop is empty and not just "all tasks before this quit closure was posted have run"?
The problem is that the tasks will themselves post future tasks (e.g. to handle the response).
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
LGTM
I mean, not really, but it's not worse and it seems unavoidable so shrug :)
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
haven't processed the messages at that point.Devon LoehrCan we just post a task to quit the run loop, or do we really need to ensure the run loop is empty and not just "all tasks before this quit closure was posted have run"?
The problem is that the tasks will themselves post future tasks (e.g. to handle the response).
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Expose RunLoop::RunUntilIdle to Rust
Previously we avoided exposing this because it's easy to misuse.
However, when testing associated interfaces we really need it,
because we need to ensure that messages _aren't_ processed while
blocked by a pending event, and the only way we can ensure that is
to run through all tasks until we run out, and then check that we
haven't processed the messages at that point.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |