gocapturedrefrace - Analyser that reports captured variable references in goroutine closures

Age	Commit message (Collapse)	Author
2023-05-15	Get assignments in closure	Teddy Wing
	Turns out this isn't what we want, as assignments means assignments. I was actually thinking of declarations.
2023-05-15	Idea for building a list of variable assignments	Teddy Wing

2023-05-15	Ignore variables from the closure's formal arguments	Teddy Wing
	Don't report variables that were passed as arguments to the closure.
2023-05-15	Find out how to get closure arguments	Teddy Wing

2023-05-15	Ideas for finding out whether a variable is a captured reference	Teddy Wing

2023-05-15	Try to limit identifier enumeration to variables	Teddy Wing
	This does ignore "strings" and "Repeat" in the "simple.go" test file.
2023-05-15	Find variables in `go func` closures	Teddy Wing
	Inspect function literals run by `go` statements, and find all variables in those function literals.
2023-05-14	Find `go` statements using Go analyzer	Teddy Wing
	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