ScopeGuard 0.0.7: Your Go-to linter for scope and shadow issues, now with MCPold.reddit.com2 ポイント·投稿者 eik·2 か月前·0 コメント
The error handling bugs that worry me aren't the ones that crashold.reddit.com1 ポイント·投稿者 eik·5 か月前·0 コメント
Minimizing Variable Scope in Go: New Blog Post and Static Analyzer Toolold.reddit.com1 ポイント·投稿者 eik·8 か月前·1 コメント
Errortype v0.0.5 Released – Now with golangci-lint Plugin Supportold.reddit.com1 ポイント·投稿者 eik·10 か月前·1 コメント
eik·5 か月前·議論ScopeGuard is a Go linter that helps you write more readable and maintainable code by suggesting tighter variable scope.
eik·8 か月前·議論Blog Post: https://blog.fillmore-labs.com/posts/scope-1/Go Analyzer: https://github.com/fillmore-labs/scopeguard#scopeguard
eik·10 か月前·議論Announcement 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 か月前·議論Yes, 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 か月前·議論The linter in the post is `err113`. `errortype` does already warn:https://github.com/fillmore-labs/errortype#errortype
eik·10 か月前·議論Having 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…