Documentation
¶
Overview ¶
Package internal implements the molint rules.
Each rule has its own file. They share one pass's state, in checker.go: the directives, the files that are generated, and the methods that implement an interface. The questions they ask of types and of SSA values live in the packages below this one.
Index ¶
Constants ¶
This section is empty.
Variables ¶
This section is empty.
Functions ¶
Types ¶
Source Files
¶
Directories
¶
| Path | Synopsis |
|---|---|
|
Package directive reads the //molint: comments in a package.
|
Package directive reads the //molint: comments in a package. |
|
Package flow follows a value back through one function, to tell whether it is a constant that a rule looks for: a nil pointer, a nil error, the constant true, or a zero mo.Result.
|
Package flow follows a value back through one function, to tell whether it is a constant that a rule looks for: a nil pointer, a nil error, the constant true, or a zero mo.Result. |
|
Package nilcheck reads what the branches above a point say about a value being nil.
|
Package nilcheck reads what the branches above a point say about a value being nil. |
|
Package rule names the rules of molint.
|
Package rule names the rules of molint. |
|
Package typeutil holds the type questions every rule asks, and the way a diagnostic spells types and declarations.
|
Package typeutil holds the type questions every rule asks, and the way a diagnostic spells types and declarations. |
Click to show internal directories.
Click to hide internal directories.