Re:Error stack traces in Go with x/xerror
by SamWhited on Tuesday August 24, 2021 @08:23AM
(#28287864)
I tend to agree, I dispute the premise that this is a problem a bit. I mean, I get not wanting to type the same thing repeatedly, but when reading code later it's really nice to have the logic explicitly in front of me and not hidden behind some other syntax or function. It could possibly be done better, but it doesn't need to be done better, IMO.
[ Parent
| on HN ]
There are no comments on this comment yet.