Correct the range of timestamp 96#301
Closed
tagomoris wants to merge 1 commit into
Closed
Conversation
|
Is it by intention that Timestamp 64 has nanoseconds specified in the upper limit and the other don't, or is it by accident? |
Member
Author
|
What does "the other" mean? For Timestamp 64, both the upper and the lower have nanoseconds.
If it means Timestamp 96, yes, it's probably intentional... but adding nanoseconds makes sense to me. |
Member
Author
|
I made a mistake about the allowed max seconds of signed 64-bit int. See #263 |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
No description provided.