Skip to content
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

(Re-)Implement executor API on top of sender/receiver infrastructure #5219

Closed
hkaiser opened this issue Mar 2, 2021 · 2 comments
Closed

Comments

@hkaiser
Copy link
Member

hkaiser commented Mar 2, 2021

Currently our executor API (customization points) dispatch to an executor interface that was defined by wg21.link/p0443R3. All HPX facilities related to scheduling tasks (algorithms, future, dataflow, async etc.) rely on the executor customization points to perform their operations.

We should reimplement the customization points such that they build upon the sender/receiver infrastructure that has been put in place in HPX based on the latest versions of wg21.link/p0443.

@msimberg
Copy link
Contributor

msimberg commented Mar 8, 2021

Thanks @hkaiser for putting this up. I think before we even consider this the bulk execution section of P0443 will need some clarity as it's currently underspecified and has quite a few proposals for improvement (and was not implemented in #5053 because of that). Hopefully r15 will specify this a bit better.

@aurianer aurianer added the category: senders/receivers Implementations of the p0443r14 / p2300 + p1897 proposals label May 6, 2021
@msimberg msimberg removed this from the 1.7.0 milestone May 21, 2021
@hkaiser hkaiser added this to the 1.8.0 milestone Jan 10, 2022
@hkaiser
Copy link
Member Author

hkaiser commented Jan 10, 2022

This can be closed as it was implemented in #5429.

@hkaiser hkaiser closed this as completed Jan 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants