| Age | Commit message (Collapse) | Author | 
|---|
|  | Second usage of captured reference is reported as expected. That seems
correct for our needs. | 
|  | Inspect function literals run by `go` statements, and find all variables
in those function literals. | 
|  | 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 |