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.
make_future: take run_loop& directly, removing the __loop_ access entirely #7248
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
make_future: take run_loop& directly, removing the __loop_ access entirely #7248
Changes from 9 commits
5a1de51fa6b723036416f1fc1401c1d87e1a3ec48867fd954644f8b2e3a968eef3c514fc83830a0c1c12File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@guptapratykshh does this comment make sense?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i removed the scheduler-based binary tag_invoke overload, the tag_override_invoke constraint is_completion_scheduler_tag_invocable_v<set_value_t, Sender, make_future_t, Allocator> evaluates to false for run-loop-backed senders, so make_future(transfer_just(sched, ...)) falls to detail::make_future which never drives the loop → hang.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you plan to do something about this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How about this comment?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
inject_scheduler partial was returned by make_future(scheduler) but had nothing to dispatch to (no binary tag_invoke(make_future_t, scheduler, sender, alloc) overload exists for any scheduler type after this PR: there only ever was one for run_loop::scheduler, which was replaced)
Uh oh!
There was an error while loading. Please reload this page.