Small changes to allow Microsecond and Tick (100 ns) resolutions #84
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
- Added Nanoseconds, Ticks and Microseconds to TimeUnit - Added TimeUnit formatting extension
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.
Summary
Discussion:
Nanoseconds and Ticks are effectively synonyms. The changes make use of the DateTime.AddTicks() function to compute differences from the epoch with a resolution of 100 nanoseconds (1 Tick).
I didn't have the time to go through the tests and see if anything needs adjusting, I only did some actual data ingress with the modified code. It would be wise to review my changes and modify/add tests as required.