-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Implement -hash and -copy of GDLLogEvent, copy on log, and don't assign extensionBytes in log writer #2204
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Implement -hash and -copy of GDLLogEvent, copy on log, and don't assign extensionBytes in log writer #2204
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
a644257
Implement -hash and -copy of GDLLogEvent
mikehaney24 ad19ba3
Copy the log object upon logging
mikehaney24 edc586a
Don't assign extensionBytes in the log writer
mikehaney24 c9c7925
Make an implicit loss of precision explicit.
mikehaney24 77ffb0a
Add a comment on performance
mikehaney24 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Precision should be irrelevant for a hash, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it matters in a theoretical sense, if the hash value of two times coincidentally have the same first 32 bits' worth of digits. In reality, it's not likely to matter, and I had to make this precision loss explicit in order to avoid a warning/lib lint failure.