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.
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
[azcore] Add ETag type to Core #15207
[azcore] Add ETag type to Core #15207
Changes from 11 commits
5671d80
bd1dfcd
8e0a9f9
0390d00
2f48548
cbad20c
24803fd
ea86e53
72f49cc
76d5720
cd5fe79
c6a099d
ae8d297
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
This doesn't handle the case of
nil
ETags per the comments.Also, I'm leaning towards having the receivers passed by reference. The reason being, if we are always defining ETags as
ETag *ETag
then calling this method will panic on anil
value. If we make the receiver and parameter byref then we can perform thenil
checks on the caller's behalf. Thoughts?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.
Fix spelling of "comparison". Remove doc sentence about "nil".
We don't want a pointer receiver because we want this to work like other fields in the struct where calling a method on nil panics - this is desired behavior.