| Age | Commit message (Collapse) | Author |
|---|
|
|
|
I don't need to use the `flags` package here for a single boolean
option. Previously I had tried with `flags` but it conflicted with the
flags defined by `analyzer.Analyzer`.
|
|
I decided I don't like the "go" prefix for a Go package name. It doesn't
make sense. Rename the module and package accordingly.
I do like the "go" prefix in the command line program, so leave it
there.
|
|
Can't figure out a way to do this while preserving the default flags of
the analyser.
|
|
|
|
|
|
Decided not to use my personal Git host directly for the module, but a
new domain specific to Go modules. This could allow me to host the code
elsewhere using a vanity module name.
|
|
Build a basic Go analyser that finds `go` statements.
Currently testing this with:
$ go run ./cmd/gocapturedrefrace ./testdata/
Using the following tutorials as a guide:
* https://arslan.io/2019/06/13/using-go-analysis-to-write-a-custom-linter/
* https://scribe.rip/codex/writing-custom-linter-in-go-54ef6f8080
|
