> Do we need to really write `or error` or whatever everywhere that all we're going to do is pass the error immediately back up the stack?
Right, exactly. Like in Go:
if (err != nil) return err
You find this littered all over every Go codebase. And somehow people seem to not realize that they’re doing the exact same thing as throwing an exception (unwinding the stack until something handles the error), just manually and painfully.
Right, exactly. Like in Go:
if (err != nil) return err
You find this littered all over every Go codebase. And somehow people seem to not realize that they’re doing the exact same thing as throwing an exception (unwinding the stack until something handles the error), just manually and painfully.