lint

Lint refers to a class of software tools that analyze source code without executing it, aiming to identify programming errors, potential bugs, stylistic inconsistencies, and suspicious constructs. The resulting feedback helps developers improve code quality, consistency, and maintainability.

The term originated from the Unix programming environment. The first lint tool, developed by Stephen C. Johnson in 1978 for the C language, searched for constructs likely to cause runtime errors. The name suggested cleaning up lint as one would remove fabric fibers from clothing.

Modern linters work by parsing source code into an abstract syntax tree or other intermediate representations, then applying a set of rules. Rules may cover syntax correctness, semantic issues, potential runtime defects, and stylistic conventions. Many languages have dedicated linters, and tools often support configurable rule sets and auto-fixes.

Examples include ESLint for JavaScript, PyLint and Flake8 for Python, RuboCop for Ruby, and golint or golangci-lint for Go. Some tools focus on style enforcement, others on security or code smells. Linters are frequently integrated into editors and continuous integration workflows to provide immediate feedback.

Limitations include occasional false positives, the need to maintain rules, and possible conflicts between rules or with evolving language features. Effective use typically involves selecting appropriate rules, ignoring benign patterns, and combining linting with other quality practices such as testing and formal code reviews.