-
Notifications
You must be signed in to change notification settings - Fork 18k
x/tools/gopls/internal/analysis/modernize: Panic in modernize/sortslice.go #71786
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
Labels
Milestone
Comments
Change https://go.dev/cl/650215 mentions this issue: |
Change https://go.dev/cl/650495 mentions this issue: |
gopherbot
pushed a commit
to golang/tools
that referenced
this issue
Feb 18, 2025
…ice: fix crash The sole statement of a comparison func body is not necessarily a return statement. + Test Fixes golang/go#71786 Change-Id: Ic002035fc9fa303b62ed1828c13f3bdfb8bc6950 Reviewed-on: https://go-review.googlesource.com/c/tools/+/650215 Reviewed-by: Robert Findley <[email protected]> Auto-Submit: Alan Donovan <[email protected]> LUCI-TryBot-Result: Go LUCI <[email protected]> (cherry picked from commit 776604a) Reviewed-on: https://go-review.googlesource.com/c/tools/+/650495 Reviewed-by: Alan Donovan <[email protected]> Auto-Submit: Robert Findley <[email protected]>
This was referenced Apr 30, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
modernize version
Installed modernize from commit 32ffaa3103522a0b05609e241d1b03b3b1abb9a6
go env
What did you do?
Running
modernize
from the master branch on my project github.com/regclient/regclient. I believe it is breaking on the following:https://github.com/regclient/regclient/blob/486aedb6664f7a4e098054581347fd89acd97578/cmd/regctl/image.go#L1226-L1234
What did you see happen?
This appears to be triggered by:
https://cs.opensource.google/go/x/tools/+/master:gopls/internal/analysis/modernize/sortslice.go;l=60;drc=a886a1c2ed0dee2af11f465e11bf48b11dda984c
What did you expect to see?
No panics.
Editor and settings
Run from the CLI.
Logs
n/a
The text was updated successfully, but these errors were encountered: