-
Notifications
You must be signed in to change notification settings - Fork 215
Instantiate the debug sender inside connect() #1070
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
Conversation
26758d3 to
6ff2d9c
Compare
6ff2d9c to
09f435b
Compare
|
/ok to test |
I can't think of a reason why this would be problematic in principle. |
| continuation_kernel<<<1, 1, 0, op.stream_>>>(std::move(op.rec_), stdexec::set_value); | ||
| } else { | ||
| continuation_kernel<cudaError_t><<<1, 1, 0, op.stream_>>>( | ||
| continuation_kernel<<<1, 1, 0, op.stream_>>>( |
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.
Some of the refactors of continuation_kernel which reordered the template parameters seem to have missed this one. The first template parameter is Receiver.
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'm pulling this change out into its own commit, since it's unrelated.
|
/ok to test |
|
/ok to test |
This doesn't build with clang-16, but does with gcc-12. Is there any reason conceptually we shouldn't be able to check the actual vs expected completions within
connect?