Speculatively implement LWG-4273 Standard execution policy types should be conventional tag class types #5578
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
StephanTLavavej
approved these changes
Aug 7, 2025
|
Thanks! I pushed extremely minor nitpicks and verified that the test is currently exhaustive. |
|
I'm mirroring this to the MSVC-internal repo - please notify me if any further changes are pushed. |
|
Tag, you're it! 😹 🎉 🤪 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Addresses #5567 (comment) for which I filed LWG-4273. IIUC we can make the changes even without corresponding changes in the standard wording.
The test suite is reworked to cover tag class types more specifically. I'm trying to cover implementation-internal construction tag types together, although the list seems messy and it might be better to make some cleanup later.