Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related issue: #935
I think there are currently too many timeout functions, with too many combinations of scheduling priority and scheduling precision (second, millisecond).
Instead of just moving every timeout function to a
futures
module, I've decided to redesign the API taking advantage of the Builder pattern and the IntoFuture trait.API example:
I'm still looking if it's possible to redesign
spawn
andidle
with the same mindset. I don't particularly like havingspawn
,spawn_local
,spawn_local_with_priority
,spawn_with_priority
,spawn_within
,spawn_within_with_priority
, ...