Run gofumpt via go tool in dprint #586
Draft
+31
−11
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.
This is a lot slower;
go tool
is faster thango run
from 1.23, but still a lot slower than a plain binary. But, this doesn't require any global installs ofgofumpt
to rundprint
. Given the recommendation is to configuregopls
to rungofumpt
instead, anddprint
does cache things, it seems like this isn't such a bad tradeoff to avoiddprint fmt
failing unexpectedly for those using that CLI.