News for hackers. Stuff that matters.

A comment on Introducing HTTP Tracing. Parent comment

Re:Introducing HTTP Tracing by rakyll on Tuesday October 04, 2016 @06:54PM (#12640290)
Avoiding error checking against a properly formatted constant is not avoiding error checking. I cannot follow your argument.
[ Parent | on HN ]
Re:Introducing HTTP Tracing by ben_jones on Tuesday October 04, 2016 @07:13PM (#12640408)
Sorry, I guess I'm not really making one. If anything I'm commenting that (IMO) explicit error handling isn't as explicit as people thing it is. There are internal errors induced by panic() that are really inconvenient.
[ Parent | on HN ]
Re:Introducing HTTP Tracing by mixedCase on Tuesday October 04, 2016 @07:37PM (#12640533)
Panics are supposed to be launched on an "end all work on this; code path is FUBAR". On a web server that usually means dropping the connection, logging everything and firing an automated e-mail to the dev team to notify there's a bug in the code that needs to be fixed.

All other error conditions are expected and handled. That's what Go's error handling philosophy is all about.

[ Parent | on HN ]
Re:Introducing HTTP Tracing by jimjimjim on Tuesday October 04, 2016 @11:05PM (#12641288)
panic should be a "the world is ending" sort of operation.
[ Parent | on HN ]