Renaming various execution things

Document #: P4154R0
Date: 2026-03-27
Project: Programming Language C++
Audience: LWG
Reply-to: Tim Song
<>
Ruslan Arutyunyan
<>
Arthur O’Dwyer
<>

1 Introduction

This paper provides replacement wording for the following papers:

This resolves the following national body comment on the C++26 CD:

and partially addresses the following national body comment on the C++26 CD:

Because there are multiple papers in flight targeting 33 [exec], LWG requested replacement wording for renames to minimize merge conflicts.

2 Wording

Instructions to the editor:

After applying all other papers moved during the Croydon meeting, please make the following replacements in 33 [exec]:

3 References

[N5032] Thomas Köppe. 2025-12-15. Working Draft, Standard for Programming Language C++.
https://wg21.link/n5032

[P3826R5] Eric Niebler. 2026. Fix Sender Algorithm Customization.
https://wg21.link/P3826R5

[P3940R0] Arthur O’Dwyer, Yi’an Ye. 2025-12-10. Rename concept tags for C++26: sender_t to sender_tag.
https://wg21.link/p3940r0

[P4031R1] Ruslan Arutyunyan. 2026. Rename system_context_replaceability namespace.
https://wg21.link/P4031R1


  1. In particular, this cross-reference is after [P3826R5] has been applied (in the current working draft [N5032], the relevant wording is located in 33.9.12.7 [exec.schedule.from]).↩︎