[time.format] A minor update for LWG 4124 #7697
Merged
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
I'm not sure what you mean here, what kind of conflicts? How would it be otherwise specified? The wording is specifying precisely the case where chrono-specs is omitted in a format-spec which uses this |
|
Oh I see what you mean, p7 says it means one thing, and p18 says otherwise. But "unless otherwise specified" is always implied. A more specific rule always overrides a more general one. This wouldn't do any harm though. |
jwakely
approved these changes
Jun 17, 2025
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.
The resolution of LWG 4124 added an exception rule for “omitting chrono-specs”, therefore [time.format] p7 should begin with “unless otherwise specified” to avoid conflicts.
This PR also added two missing commas in [time.format].