-
Notifications
You must be signed in to change notification settings - Fork 18.1k
x/tools/gopls: support non-vet analyses #36639
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
Comments
Thanks for raising this issue! I think we can expand its scope to include all of the analyses in https://github.com/golang/tools/tree/master/go/analysis/passes. @ianthehat, @matloob: Is there any reason we haven't added them before / any reason to exclude them? |
I don't know what the reason was that we hadn't added them before, but my guess was that we started conservative when we added the initial set, and just neglected to add others when we expanded the set of analyses we used to include non-vet analyses. |
Change https://golang.org/cl/215677 mentions this issue: |
…uite The LSP already supports a bunch of analyses we have less confidence in than the vet suite so we should add these too. Updates golang/go#36639 Change-Id: Ifc37d09e3acd73de021be7b45b3d80fe8c00e0d7 Reviewed-on: https://go-review.googlesource.com/c/tools/+/215677 Run-TryBot: Michael Matloob <[email protected]> Reviewed-by: Rebecca Stambler <[email protected]> TryBot-Result: Gobot Gobot <[email protected]>
Closing this issue as we've added |
Change https://golang.org/cl/219203 mentions this issue: |
The nilness analyzer requires SSA, which is very expensive to build and uses a lot of RAM. It also seems to really shoot up memory usage when it hits certain cases, which is causing a lot of problems for users. Disable this analysis - we'll leave SSA to staticcheck. Updates golang/go#36639 Change-Id: I46e67a6fd7828a5fddcd42d1aa00876f17c79e3d Reviewed-on: https://go-review.googlesource.com/c/tools/+/219203 Run-TryBot: Rebecca Stambler <[email protected]> TryBot-Result: Gobot Gobot <[email protected]> Reviewed-by: Heschi Kreinick <[email protected]>
Change https://golang.org/cl/219223 mentions this issue: |
The nilness analyzer requires SSA, which is very expensive to build and uses a lot of RAM. It also seems to really shoot up memory usage when it hits certain cases, which is causing a lot of problems for users. Disable this analysis - we'll leave SSA to staticcheck. Updates golang/go#36639 Change-Id: I46e67a6fd7828a5fddcd42d1aa00876f17c79e3d Reviewed-on: https://go-review.googlesource.com/c/tools/+/219203 Run-TryBot: Rebecca Stambler <[email protected]> TryBot-Result: Gobot Gobot <[email protected]> Reviewed-by: Heschi Kreinick <[email protected]> (cherry picked from commit 2ee7536) Reviewed-on: https://go-review.googlesource.com/c/tools/+/219223
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
What did you expect to see?
just like https://github.com/golang/tools/tree/master/go/analysis/passes/nilness
support nilness detection for code analysis
What did you see instead?
The text was updated successfully, but these errors were encountered: