ScopeGuard 0.0.7: Your Go-to linter for scope and shadow issues, now with MCPold.reddit.com2 points·by eik·2 個月前·0 comments
The error handling bugs that worry me aren't the ones that crashold.reddit.com1 points·by eik·5 個月前·0 comments
Minimizing Variable Scope in Go: New Blog Post and Static Analyzer Toolold.reddit.com1 points·by eik·8 個月前·1 comments
Errortype v0.0.5 Released – Now with golangci-lint Plugin Supportold.reddit.com1 points·by eik·10 個月前·1 comments
eik·5 個月前·discussScopeGuard is a Go linter that helps you write more readable and maintainable code by suggesting tighter variable scope.
eik·8 個月前·discussBlog Post: https://blog.fillmore-labs.com/posts/scope-1/Go Analyzer: https://github.com/fillmore-labs/scopeguard#scopeguard
eik·10 個月前·discussAnnouncement of the release of errortype v0.0.5, a Go linter that helps catch subtle bugs in error handling.https://github.com/fillmore-labs/errortype#errortype
eik·10 個月前·discussYes, but “an Is method should only shallowly compare err and the target and not call Unwrap on either”:https://pkg.go.dev/errors#Is
eik·10 個月前·discussThe linter in the post is `err113`. `errortype` does already warn:https://github.com/fillmore-labs/errortype#errortype
eik·10 個月前·discussHaving looked at the problems that can arise with errors.As:https://news.ycombinator.com/item?id=44959638Let's now look at how errors.Is can introduce subtle bugs that can affect the reliability of error checking, especially when trying to determine the root cause of an error.How one letter can make such a difference…