5 ms·
You soon get used to the pattern: blah, err := foo(...) if err != nil { return nil, err } and it's sister: blah, err := foo(wibble) if er
by sambeau 13y ago
You soon get used to the pattern:
blah, err := foo(...)
if err != nil {
return nil, err
}
and it's sister:
blah, err := foo(wibble)
if err != nil {
return nil, errors.New("foo error with blah due to: " + wibble)
}
After a while I got to like passing errors carefully back up the call stack , cleaning them up, rewriting them and making them more useful.
My Go programs have far better (more detailed & relevant) error messages than any of my other code.
- masklinn 13y ago> You soon get used to the pattern: Yes, we all know how good humans are at work which no computer could ever do such as repetitive output of pointless generic boilerplate.
- sambeau 13y agoMy point is that translating an error from one call to the previous is neither generic nor pointless. An exception and line-number (and a call-stack dump) is great for a developer, but a good textual error message is needed for a real user.
- zellyn 13y agoI agree with sambeau on this one. I have come to like the go way of doing things: it's extremely simple, doesn't take much thought, and after a little while is very easy to read.
- masklinn 13y ago> My point is that translating an error from one call to the previous is neither generic nor pointless. The first pattern does not do that. The second one is still mostly pointless generic boilerplate: blah, err := if err != nil { return nil, errors.New() } is all boilerplate, only two parts are not: the call itself and the error message. > An exception and line-number (and a call-stack dump) is great for a developer, but a good textual error message is needed for a real user. 1. having exceptions doesn't preclude handling them and writing user-readable error messages 2. exceptions are not the only alternative to C-style error handling
- notok22 13y agoCan you tell me about the other alternatives? I'm actually interested in this and I have searched for alternatives at least to see how they look.
- masklinn 13y agoI'm sure I don't know most of them (e.g. I have no idea how Prolog does error handling), but I know of: * the Haskell/ML statically typed approach, error possibility is type-encoded through an Option or Either type; even in cases where it is possible to implicitly ignore return values[0] the compiler will warn or error; the standard library provides high-level operations to pipeline results (build a pipeline of operations which will only transform non-erroneous results, and will let errorneous ones go through) * the Erlang dynamically typed approach which makes use of tagged pattern matching to make value assertions trivial. It is not shorter than the Go version when fully handling things, but assertion can be used to fault processes during development or when in-process user-visible reporting is irrelevant (fairly common in erlang) yet remain easy to find and replace with more involved handling if needs be [0] because haskell strives for purity, ignoring return values in non-monadic code makes very little sense and I'm not sure it's possible at all short of unsafe* functions. It is possible in monadic code (e.g. do blocks)
- AYBABTME 13y agoYou might like: _, err := somethingThatFails(arg) if err != nil { return fmt.Errorf("failed with arg=%v, %v", arg, err) } Now the use for this is not obvious from this toy example, but having a `printf`-like function that produces error is great to return errors with more context. The difference from your example is that the info in `err` is not lost when passed up.
- sambeau 13y agoI do like that. (I just picked (and cleaned up) the first piece of simple error code that I thought would be easy to use.)
- benmanns 13y agoAnd you might like: if _, err := somethingThatFails(arg); err != nil { return fmt.Errorf("failed with arg=%v, %v", arg, err) }
- AYBABTME 13y agoIn that case I was ignoring the returned value for the sake of the example, otherwise you lose the declaration when it's in a `if`.