Alan Donovan
Alan Donovan
As documented [here](https://github.com/bazelbuild/rules_go/blob/master/go/nogo.rst#configuring-analyzers), the nogo BUILD rule allows you to declare a config=... configuration in a JSON file. Is this not sufficient? If not, why not? Is the problem that...
> I don't think the current setup is suitable to scale up to O(n) number of Analyzer, certainly not if we started to add 1 new config file for each...
x/tools/go/pointer was deleted; see #59676.
I just tested this renaming in gopls (not the obsolete cmd/gorename) from Emacs and VS Code and it works correctly in both. Closing as not reproducible.
As @jamalc pointed out, this is a bug in golangci-lint: it appears to be running `go list ./...`, which is not going to work in a tree that has a...
Perhaps the new names should include an At suffix to make clear to casual readers of the API that these are not the usual open system calls. Either way, the...
Fair enough. Should the `fs.OpenFile.Open` method also be named `OpenIn`?
That wouldn't be a compatible change. If we add the field, then a driver that hasn't implemented support for it yet will run analyzers unconditionally, despite their RequiresModule declaration, so...
Option 3. If the pass is running, it means we got a package (possibly with errors if RunDespiteErrors). The analyzer can deal with them.
> Maybe related, a recent very minimal CL (not yet submitted) to forward module path information from vet (which already contains module version). https://go.dev/cl/571016. Perhaps that CL should be revised,...