Adam Jones

Thanks for the quick, detailed, and illuminating reply—I appreciate it. Thanks for your work on `gofumpt`, as well. It's a wonderful tool. --- > Put simply, if someone really wants...

> Arguably, that may be a problem for more than just formatting. If your work project builds and tests with Go 1.18, you should also use your tools (formatting, static...

Yes, quite right—sorry. It's all a bit tricky! Perhaps the least bad solution would be: - for each gofumpt tag, provide a range of supported Go versions (which looks to...

> I'm less convinced that providing so many gofumpt binaries will be a net benefit. My guess is that it would confuse users more than anything. We should recommend using...

I've now rebased the branch onto the current version of main. I don't know how the CI system is set up in this repo. Is the "kokoro" step causing it...

I'm also affected by this. Your branch fixes the issue for me—thanks.

I had a similar issue (Pixel 4a to Pixel 7a) and the build as of 76cd8b5 fixed it for me—thanks for the pointer.

I think that's an excellent idea. zstd in particular has [a strong appeal to it](https://insanity.industries/post/pareto-optimal-compression/). It's especially appealing with NSQ as it seems like a common pattern is for a...

Thanks for getting back to me—I agree about the shape an appropriate prompt ought to have and that documentation is probably the best approach. I know that the above example...

I'd be up for trying to introduce the feature; it may take a little while to find the time to finish it. Before I embark, which do you think matches...