Question 1

How to integrate go-critic with golangci-lint?

Accepted Answer

go-critic is commonly used as part of golangci-lint; enable it in the golangci-lint configuration file to leverage its checkers alongside other linters seamlessly, as recommended in the README for most users.

Question 2

go-critic vs staticcheck: which is better for Go code analysis?

Accepted Answer

go-critic focuses on opinionated and extensible checks with dynamic rules, while staticcheck is more conservative and widely adopted for reliable diagnostics; choose go-critic for strict enforcement and custom rules, staticcheck for standard, battle-tested analysis.

Question 3

How to disable specific checkers in go-critic?

Accepted Answer

Use the `-disable` flag with checker names or tags, e.g., `-disable=appendAssign` or `-disable='#opinionated'`, as shown in the usage examples, to tailor linting to your project's needs.

Question 4

What are the best go-critic checkers for performance optimization?

Accepted Answer

Checkers in the #performance tag, such as rangeExprCopy, help identify potential bottlenecks; run `go-critic doc` on specific checkers for details, and enable them with `-enable='#performance'` for focused audits.

Question 5

How to write custom rules for go-critic using ruleguard?

Accepted Answer

Define rules in Go files with ruleguard syntax, then use go-critic's dynamic rules feature to load them without recompilation; refer to the ruleguard documentation linked in the README for implementation steps.

Question 6

Does go-critic work with Go modules?

Accepted Answer

Yes, go-critic fully supports Go modules and can analyze packages in module-based projects without issues, as it operates on standard Go source code paths and commands.

go-critic

What is go-critic?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions