3 ms·

I also like errors as values, I just wish there was a syntactically simpler way to express "let the caller of this function deal with the error".

• lionkor 3y ago
  like Zigs `try xyz();` which does what you say
  • packetlost 3y ago
    Or Rust's `?`. The problem is Go returns errors by conventional multiple-returns/tuples, not by language construct.
    • lionkor 3y ago
      it could do something sane but smart, like returning the error for whatever argument is an error type, and nil the rest.