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
crypto/x509: apply gofmt to verify.go #35052
Comments
Probably the result of some earlier fine-tuning of the fmt algorithms. They are not guaranteed to give the exact same output accross Go releases, although any adjustments tend to be minor in character. It will get fixed up the next time someone touches that file in the course of doing some actual work. Until that happens, the current state doesn't hurt anyone, I guess? |
Yeah I was just surprised |
You are most welcome to send a patch. |
Seems to require having google account and signing CLA, so I leave it up to someone willing to put up with both. |
I can easily claim this and send a patch. |
Change https://golang.org/cl/202877 mentions this issue: |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
What did you expect to see?
What did you see instead?
The text was updated successfully, but these errors were encountered: