[time.zone.leap.members] update note about leap seconds #6016
Conversation
This file contains 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
jensmaurer
approved these changes
Dec 13, 2022
|
Somehow I feel we should change the note so that it doesn't become invalid for every standards release. But the proposed adjustment is better than no change at all. |
|
It looks like the next leap second might be negative, so we would need to either remove or change it to a definite statement about the past. But there might be three standard releases before that actually happens. |
|
I thought leap seconds are now abolished? |
|
There is agreement to stop adding them after 2035, but that still has to be ratified by the ITU. Even if the ITU agrees, there could be more leap seconds added before 2035. |
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.
This note about leap seconds is still true, but should be updated to be more precise. Saying something about 2019 in C++23 seems odd, and will lead readers to wonder if a negative leap seconds was inserted in 2020.
There has been no leap second inserted since 2016, and none will be inserted before 2023-06-28 at the earliest.
https://en.wikipedia.org/wiki/Leap_second