Trendy named return linter? – Technical Dialogue

What’s a Go 1.24.1 appropriate named return linter?

Neither golangci-lint (nakedret, nonamedreturn), lint-naked-returns, nor returnstyles have up to date their x dependencies to account for breaking compilation modifications.

As an apart, Go ought to weaken its backwards compatibility ensures, or else merge the x libraries into stdlib, for futureproofing.

As of late April 2025, a available Go 1.24.1 appropriate named return linter is probably going unavailable as a consequence of outdated x dependencies in in style choices like golangci-lint and returnstyles. Your greatest guess is to observe these linters for updates on their GitHub repositories or briefly use an older Go model if strict 1.24.1 compatibility isn’t instantly crucial. Constructing a customized linter is a extra concerned various. The broader concern of Go’s backward compatibility and the x libraries is a identified trade-off within the Go ecosystem.

1. A linter that enforces named return values (in a language like Go)?
2. A contemporary linter that checks for points with named return values?
3. A linter named “Named Return” (maybe a selected software)?
4. One thing else solely?

Normally, right here’s a fast overview which may hit what you’re asking:

What Are Named Return Values?

func calculate(a int, b int) (sum int, diff int) {
    sum [=](https://hell-starsclothing.com/) a + b
    diff = a - b
    return // implicit return of named values
}

Linters for Named Returns

1. Staticcheck

• A robust Go linter.
• Flags pointless named return values or warns once they’re utilized in complicated methods.
• https://staticcheck.io/

2. golangci-lint

Instance Rule You Would possibly Need

I’m asking as a result of these very linters are inoperable with every successive Go launch. The x dependencies introduce breaking modifications which the linter maintainers are lax on maintaining with.