Switch Clock to BigInt and fix monotonicity #175
Merged
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.
Due to reduction of accuracy of the hrtime based clock to microseconds, the clock was no longer monotonic.
This fixes that, makes use of
hrtime.bigint()
(see #72 (comment)) and removes the decimal-encoded clock accuracy, which was not preserved for high clock ticks anyway (only up to ~30 years, which is likely still sufficient, but not guaranteed).Also, this adds tests for the Clock to verify monotonicity and that it can cover at minimum 100 years (from it's epoch into the future).