Add 2015 leap second #27
Merged
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
I noticed that when calculating dates after the last leap second in the table, a user warning is issued. This is good, as I otherwise would not have known that leap seconds are handled as a constant. This patch adds the 2015 leap second to the constant list, bringing it up to date.
pingswept
added a commit
that referenced
this pull request
Mar 28, 2015
Add 2015 leap second. Thanks, Naz!
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.
I noticed that when calculating dates after the last leap second in the
table, a user warning is issued. This is good, as I otherwise would not
have known that leap seconds are handled as a constant.
This patch adds the 2015 leap second to the constant list, bringing it
up to date.