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.
What changed?
This PR adds easy access to Zap's Stringer and Stringers fields.
Why?
Stringer
fields are more efficient thanString
field. In the OSS repo alone we have 22 separate invocations oftag.NewStringTag(..., foo.String())
which would be better served by using a Stringer tag. This only callsString
(which can be expensive) when the line is actually emitted.Meaning fewer wasted cycles when calling
String()
for debug-level logs.How did you test it?