Mark Rousskov 0127704c98 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

2018-07-26 09:18:25 -06:00

..

context.rs

Split libcore/task.rs into submodules

2018-06-26 16:40:42 +02:00

executor.rs

Clarify what a task is

2018-07-25 13:39:14 +02:00

mod.rs

Add lifetime to FutureObj

2018-07-02 13:59:40 +02:00

poll.rs

Split libcore/task.rs into submodules

2018-06-26 16:40:42 +02:00

wake.rs

Forget Waker when cloning LocalWaker

2018-07-23 13:45:25 +02:00