eik

Joined 2 years ago

Karma

17

Submissions

16

Member since

Sep 2

View on Hacker News

Recent submissions

ScopeGuard 0.0.7: Your Go-to linter for scope and shadow issues, now with MCP old.reddit.com

2 eik 6 months ago 0 comments

The error handling bugs that worry me aren't the ones that crash old.reddit.com

1 eik 8 months ago 0 comments

Comment · 9 months ago

ScopeGuard is a Go linter that helps you write more readable and maintainable code by suggesting tighter variable scope.

ScopeGuard v0.0.5: Improved Shadow Detection old.reddit.com

1 eik 9 months ago 1 comments

Go: Nested Assignments and New ScopeGuard Version old.reddit.com

1 eik 10 months ago 0 comments

ScopeGuard 0.0.2 – Go analyzer for tighter scopes old.reddit.com

2 eik 11 months ago 0 comments

Comment · 11 months ago

Blog Post: https://blog.fillmore-labs.com/posts/scope-1/

Go Analyzer: https://github.com/fillmore-labs/scopeguard#scopeguard

Minimizing Variable Scope in Go: New Blog Post and Static Analyzer Tool old.reddit.com

1 eik 11 months ago 1 comments

Comment · 1 year 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

Errortype v0.0.5 Released – Now with golangci-lint Plugin Support old.reddit.com

1 eik 1 year ago 1 comments

Comment · 1 year 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

Comment · 1 year ago

The linter in the post is `err113`. `errortype` does already warn:

https://github.com/fillmore-labs/errortype#errortype

Comment · 1 year 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, especially when trying to determine the root cause of an error.

How one letter can make such a difference…

The Day the Linter Broke My Code blog.fillmore-labs.com

25 eik 1 year ago 6 comments

Comment · 1 year 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 mechanics, point out how the dynamic type (pointer vs. value) matters, and offer a simple, effective two-step approach to prevent these silent bugs.