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

Adapt executor implementation to P0443R2 #2691

Closed
3 of 14 tasks
hkaiser opened this issue Jun 11, 2017 · 1 comment
Closed
3 of 14 tasks

Adapt executor implementation to P0443R2 #2691

hkaiser opened this issue Jun 11, 2017 · 1 comment

Comments

@hkaiser
Copy link
Member

hkaiser commented Jun 11, 2017

This involves a couple of steps. The (currently still evolving) document can be found here: https://github.com/executors/issaquah_2016/blob/R2/wording.md

  • clean up existing executor categories and corresponding traits (P0443 r2 #2693)
  • rename <op>_bulk_execute to bulk_<op>_execute (P0443 r2 #2693)
  • implement BaseExecutor requirement on all existing executors
  • implement traits has_<op>_member<T> (P0443 r2 #2693)
  • implement traits has_<op>_free_function<T>
  • support free functions when invoking executors (use traits above to distinguish)
  • implement traits reporting on customization points can_<op><T>
  • implement task_block overload taking executor (as an alternative to the existing overload taking an execution policy)
  • add executor_execution_mapping_guarantee
  • add executor_execute_blocking_guarantee
  • add executor_bulk_forward_progress_guarantee
  • implement polymorphic executor wrappers
  • implement default one_way_executor, two_way_executor, and never_blocking_one_way_executor
  • implement non-variadics interface requirements of P0443R2 on top of our variadic interfaces
@hkaiser hkaiser added this to the 1.1.0 milestone Jun 11, 2017
@msimberg msimberg removed this from the 1.1.0 milestone Dec 5, 2017
@hkaiser hkaiser added the tag: pinned Never close as stale label Jun 30, 2019
@msimberg
Copy link
Contributor

msimberg commented Jan 5, 2021

@hkaiser we can probably close this now? I think it's unlikely that we'll go back and fill in the gaps for an old proposal. We can track the current progress in #5045.

@hkaiser hkaiser closed this as completed Jan 5, 2021
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

2 participants