eik

4 ms·

1.
ScopeGuard 0.0.7: Your Go-to linter for scope and shadow issues, now with MCP(old.reddit.com)
2 points by eik 5mo ago|0 comments
2.
The error handling bugs that worry me aren't the ones that crash(old.reddit.com)
1 points by eik 7mo ago|0 comments
3.
ScopeGuard v0.0.5: Improved Shadow Detection(old.reddit.com)
1 points by eik 8mo ago|1 comments
4.
by eik 8mo ago
ScopeGuard is a Go linter that helps you write more readable and maintainable code by suggesting tighter variable scope.
5.
Go: Nested Assignments and New ScopeGuard Version(old.reddit.com)
1 points by eik 9mo ago|0 comments
6.
ScopeGuard 0.0.2 – Go analyzer for tighter scopes(old.reddit.com)
2 points by eik 10mo ago|0 comments
7.
Minimizing Variable Scope in Go: New Blog Post and Static Analyzer Tool(old.reddit.com)
1 points by eik 10mo ago|1 comments
8.
by eik 10mo ago
Blog Post: https://blog.fillmore-labs.com/posts/scope-1/ Go Analyzer: https://github.com/fillmore-labs/scopeguard#scopeguard
9.
Errortype v0.0.5 Released – Now with golangci-lint Plugin Support(old.reddit.com)
1 points by eik 1y ago|1 comments
10.
by eik 1y ago
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
11.
by eik 1y ago
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
12.
by eik 1y ago
The linter in the post is `err113`. `errortype` does already warn: https://github.com/fillmore-labs/errortype#errortype
13.
The Day the Linter Broke My Code(blog.fillmore-labs.com)
25 points by eik 1y ago|6 comments
14.
by eik 1y ago
Having looked at the problems that can arise with errors.As: https://news.ycombinator.com/item?id=44959638 Let's now look at how errors.Is can introduce subtle bugs that can affect the reliability of error checking, es
15.
Understanding Go Error Types: Pointer vs. Value(blog.fillmore-labs.com)
5 points by eik 1y ago|1 comments
16.
by eik 1y ago
I recently dove deep into an unexpectedly tricky issue in Go error handling — how using errors.As with pointers vs. values can silently change program behavior, and I wanted to share what I learned. The Blog Post I walk through the core mec