Alex Crichton 293d104177 Remove Future::schedule ...

A more appealing model is actually just automatically inferring what needs to be
scheduled based on what actions are done during poll. For example if during a
poll you check a oneshot channel, then the current task is registered for being
woken up if it's not ready. Similarly this will apply to I/O where if I/O is
attempted but we see EAGAIN then we'll schedule the task to get notified when
it's ready.

This may also have performance benefits in some niche situations because you
don't need to recompute where you are in the state machine both during poll and
during schedule. Instead, it now happens all at once.

2016-08-17 18:41:34 -07:00

..

buffered.rs

Let's rename everything!

2016-07-30 22:50:58 -07:00

chain.rs

Let's rename everything!

2016-07-30 22:50:58 -07:00

echo.rs

Remove Future::schedule

2016-08-17 18:41:34 -07:00

limit.rs

Let's rename everything!

2016-07-30 22:50:58 -07:00

stream-buffered.rs

Keep polling in Buffered if there's more futures

2016-08-15 16:22:09 -07:00

tcp.rs

Let's rename everything!

2016-07-30 22:50:58 -07:00

timeout.rs

Add a timer wheel

2016-08-03 22:57:07 -07:00

udp.rs

Add a simple UDP test

2016-08-02 23:56:01 -07:00