https://github.com/mvdan/unparam

Find unused parameters in Go
https://github.com/mvdan/unparam

arguments functions go linter parameters results unused

Last synced: about 1 month ago
JSON representation

Find unused parameters in Go

• Host: GitHub
• URL: https://github.com/mvdan/unparam
• Owner: mvdan
• License: bsd-3-clause
• Created: 2017-03-04T12:22:48.000Z (over 7 years ago)
• Default Branch: master
• Last Pushed: 2024-04-27T19:52:14.000Z (about 2 months ago)
• Last Synced: 2024-05-01T21:59:19.039Z (about 2 months ago)
• Topics: arguments, functions, go, linter, parameters, results, unused
• Language: Go
• Homepage:
• Size: 233 KB
• Stars: 502
• Watchers: 10
• Forks: 28
• Open Issues: 8
• Metadata Files:
  • Readme: README.md
  • Funding: .github/FUNDING.yml
  • License: LICENSE

Lists

• awesome-go-linters - unparam - Report unused function parameters. (Linters / Unused Code)
• static-analysis - unparam
• awesome - unparam - Find unused parameters in Go (Go)

README

        
# unparam

	go install mvdan.cc/unparam@latest

Reports unused function parameters and results in your code.

To minimise false positives, it ignores certain cases such as:

* Exported functions (by default, see `-exported`)

* Unnamed and underscore parameters (like `_` and `_foo`)

* Funcs that may satisfy an interface

* Funcs that may satisfy a function signature

* Funcs that are stubs (empty, only error, immediately return, etc)

* Funcs that have multiple implementations via build tags

It also reports results that always return the same value, parameters

that always receive the same value, and results that are never used. In

the last two cases, a minimum number of calls is required to ensure that

the warnings are useful.

False positives can still occur by design. The aim of the tool is to be

as precise as possible - if you find any mistakes, file a bug.