2 ms·

You surely know that it is very common to rethrow the original exception wrapped in languages with try-catch — it still saves you the time to write that (plus i

• Xeoncross 4y ago
  I've written a lot of try/catch but no one in those languages do that for every branch, it's usually just everything wrapped in a big try/catch. Go makes you deal with the error every single time something could go wrong, so you have a chance to do the right thing and append context at every single failure path.
  • kaba0 4y ago
    Go makes you believe you dealt with the error, but instead you just forget about it. Also, checked exceptions are very much not like that, and being able to handle errors of a logical unit is also beneficiary (e.g. transactions). You are free to use the scope-size that makes sense for the given use case.
    • Xeoncross 4y ago
      > Go makes you believe you dealt with the error, but instead you just forget about it. Can you explain that? Touching every context of an error propagation seems opposite of forgetting about it.