News for hackers. Stuff that matters.

A comment on I want off Mr. Golang’s Wild Ride (2020). Parent comment

Re:I want off Mr. Golang’s Wild Ride (2020) by dosethree on Thursday April 28, 2022 @02:42PM (#31196510)
I've ran into bugs multiple times because I ignored an error result, or overwrote the "err" variable and swallowed an error. Errcheck helps a bit.

Other languages that have exceptions that bubble up the stack have a few advantages (easier to instrument with monitoring, stack traces and line numbers out of the box) but developers often misuse error handling as flow control

[ Parent | on HN ]
Re:I want off Mr. Golang’s Wild Ride (2020) by preseinger on Friday April 29, 2022 @09:51PM (#31212654)
> I've ran into bugs multiple times because I ignored an error result, or overwrote the "err" variable and swallowed an error. Errcheck helps a bit.

Any reasonable code review process would catch these (very obvious) problems.

[ Parent | on HN ]
Re:I want off Mr. Golang’s Wild Ride (2020) by dosethree on Sunday May 01, 2022 @02:03PM (#31227203)
my golang code is littered with err handling etc, it’s easy to miss something over the course of dozens of prs. This is something best caught at compile time or by a linter. Or tests which I am often lacking

I find code review unreliable at best for catching bugs or logic errors, but depends on the reviewer

[ Parent | on HN ]