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.
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.