Re:Next steps toward Go 2
by pacala on Wednesday June 26, 2019 @03:37PM
(#20288360)
The example was a worst case example. There are weaker versions thereof, for example the familiar:
The principle stays the same, there is not much to "handle" and no option to recover without external help, either by providing a well-formed request for 400 errors or by providing well-behaving code for 500 errors.
[ Parent
| on HN ]
If an error is unrecoverable, panic. If all you're trying to do is generate a 500 error, net/http even handles the panic for you. If you're a library author and unsure of whether your callers want a panic or not, provide a normal and an (idiomatic) "Must" version that panics on the error.
There are legitimate criticisms to be made of how Go's error handling works, but I think the language already handles the case you're talking about.