nonamedreturns icon indicating copy to clipboard operation
nonamedreturns copied to clipboard

golang linter to detect named returns

Results 3 nonamedreturns issues
Sort by recently updated
recently updated
newest added

Names return values are useful for documentation, but problematic when those variables are actually used because of mutation. I would propose a option to the linter to allow naming return...

The release (v1.0.4) is not a bugfix release, it's a breaking change: a major version must be created. Also, the previous release (v1.0.2) was also wrong, because it's not a...

I hate named returns too :) Well, one case are good and should be allowed by linter I suppose. ``` go func f() (retErr error) { err := errors.New("foo") defer...