You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The guru command used to have a whicherrs query that:
reports the set of possible constants, global variables, and concrete types that may appear in a value of type error.
In our work projects we try and follow the Whether to wrap section of the Working with Errors in Go 1.13 blog post. We have some legacy code that we've had to convert to wrapping unconditionally and something like whicherrs would greatly help us understand where it's safe to stop doing that.
The text was updated successfully, but these errors were encountered:
Issues related to the Go language server, gopls.
This label describes issues relating to any tools in the x/tools repository.
Oct 16, 2023
Clever though it was, whicherrs was one of many features of guru that relied on pointer analysis, which we made the decision to stop supporting because of the inherent problems of that technology described in #59676. So I don't think this is a feature of guru that anyone should attempt to bring back, at least not using its previous approach.