New function timestamp_usec #316
Merged
Conversation
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
codyps
force-pushed
the
timestamp_u64
branch
4 times, most recently
from
d8134ec to
83f17fc
Compare
|
Sorry about changing around the name, I wanted to communicate the units of the return value in the name of the function. I considered Thanks for the PR. |
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.
Hello,
This is a great crate, but I need a function that I want to share.
I created the function pub fn timestamp_usec(&self) -> Result on JournalRef struct. It the same than the timestamp, but it gives a direct access to the realtime_usec u64 value.
I also made a test to ensure that both functions "timestamp_usec" and "timestamp" return the same.
Thank you
PS
Without this function I can still get the u64 value with the help of workarounds ;)