ran gofmt @ v1.17, these are the resulting changes #10362
Merged
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
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.
Go updated the formatting for build tags in the 1.17 release, but these changes aren't reflected currently in the codebase. The impact of this is that running gofmt creates a bunch of noisy diffs.
What type of PR is this?
Other
What does this PR do? Why is it needed?
These changes keep popping up when I run gofmt using a 1.17. I want to commit separately to reduce noise.
Other notes for review
Based on go.mod we should all safely be on go version >= 1.17.