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.
I'm currently working on moving the hyper 0.12.x branch over to the futures 0.2 alpha release.
As part of this, I'm starting to notice a few places where I would like to get hold of
task::Context
without needing to write a special future for it.Here is an example:
I tried using
poll_fn
, since that gives me thetask::Context
as an argument, but since it has aFnMut
it doesn't work for most of cases I've tried.Therefore I would like to propose this change, introducing
task::Context
as an argument to the closure passed in tolazy
, similar to how it works forpoll_fn
.Let me know what you think!