diff options
| author | Mark Rousskov <mark.simulacrum@gmail.com> | 2018-07-26 09:18:25 -0600 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-07-26 09:18:25 -0600 |
| commit | 0127704c984ad99f113e7f8b1adeb47994acac6d (patch) | |
| tree | 2d7d3fa00decaa8db36d093f8b34f528a0a17a89 /src/test/incremental/thinlto | |
| parent | e29f15bafd08f306fd1255131003468f4ace71e9 (diff) | |
| parent | eacfd7252252fac66b9354cdd861f054cc678373 (diff) | |
| download | rust-0127704c984ad99f113e7f8b1adeb47994acac6d.tar.gz rust-0127704c984ad99f113e7f8b1adeb47994acac6d.zip | |
Rollup merge of #52610 - MajorBreakfast:task-terminology, r=cramertj
Clarify what a task is
Currently we call two distinct concepts "task":
1. The top-level future that is polled until completion
2. The lightweight "thread" that is responsible for polling the top-level future. What additional data beside the future is stored in this type varies between different `Executor` implementations.
I'd prefer to return to the old formulation by @alexcrichton:
```rust
/// A handle to a "task", which represents a single lightweight "thread" of
/// execution driving a future to completion.
pub struct Task {
```
Source: [`task_impl/mod.rs` in futures-rs 0.1](https://github.com/rust-lang-nursery/futures-rs/blob/1328fc9e8af5737183df477c7501e6ea24ff2053/src/task_impl/mod.rs#L49-L50)
I think that this change will make it much easier to explain everything.
r? @aturon
@cramertj
Diffstat (limited to 'src/test/incremental/thinlto')
0 files changed, 0 insertions, 0 deletions