firefart / nonamedreturnsLinks
golang linter to detect named returns
☆28Updated 2 weeks ago
Alternatives and similar repositories for nonamedreturns
Users that are interested in nonamedreturns are comparing it to the libraries listed below
Sorting:
- Golang linter to use strconv☆40Updated 4 months ago
- A linter that handles struct tags.☆54Updated 3 months ago
- 🚔 Enforce field tags in (un)marshaled structs☆38Updated 2 weeks ago
- ☆53Updated 9 months ago
- A linter to ensure that slices are not initialized with non-zero length☆76Updated 6 months ago
- intrange is a program for checking for loops that could use the Go 1.22 integer range feature.☆33Updated this week
- Accept Interfaces, Return Concrete Types☆74Updated 2 months ago
- Golang linter that encourages you to use a separate _test package☆51Updated last week
- The Golang linter that checks that sentinel errors are prefixed with the `Err` and error types are suffixed with the `Error` or `Errors`.☆26Updated 3 weeks ago
- linter for copyright headers☆27Updated 2 weeks ago
- tparallel finds inappropriate usage of `t.Parallel()` method in your Go test codes☆26Updated last year
- Analyzer: fourcetypeassert finds type assertions which did forcely☆42Updated 5 months ago
- Linter that checks that comments end in a period☆48Updated 3 months ago
- Go linter for forbidding identifiers☆147Updated 6 months ago
- Go linter to detect erroneous multiplication of duration values☆48Updated last year
- Linter to check if your tests have been marked as parallel correctly☆57Updated 4 months ago
- The Golang linter that checks that there is no simultaneous return of `nil` error and an invalid value.☆68Updated 3 weeks ago
- Golang linter to check the errors handling expressions☆55Updated 4 years ago
- misspelled word linter for Go comments, string literals and embedded files☆42Updated 4 months ago
- Simple linter to check that your code does not contain non-ASCII identifiers☆27Updated 2 weeks ago
- detects nested contexts in loops or function literals☆48Updated last week
- Go analyzer checking that the length of a variable's name matches its usage scope☆22Updated last year
- Detect deeply nested if statements in Go source code☆43Updated 3 years ago
- Linter that confirms DB rows and statements are closed properly.☆87Updated 2 months ago
- An analyzer that checks for pointers to enclosing loop variables.☆38Updated last year
- Checks for a new line before return and branch statements.☆28Updated last year
- Go linter for Vertical Function Ordering☆18Updated last month
- Check that no globals are present in Go code.☆118Updated 2 months ago
- ☆43Updated 7 months ago
- The open2opaque tool migrates Go packages from the Go Protobuf Open Struct API to the Opaque API.☆22Updated last month