2 ms·
As a primarily Go dev - 100% agree. The endless check and wrap error results in long chains of messages you have to grep for to understand the call stack. For w
by Fizzadar 9mo ago
As a primarily Go dev - 100% agree. The endless check and wrap error results in long chains of messages you have to grep for to understand the call stack. For what benefit? Might as well just panic and recover/log the stack in many cases.
- formerly_proven 9mo agoArtisanal callstacks
- deleted 9mo ago[deleted]
- morshu9001 9mo agoThe error handling is by far my least favorite aspect of Go. It's tedious and dangerous. It should either be like Rust or like JS, there isn't a good third option.
- tcfhgj 9mo agowhat about checked exceptions (Java)?
- morshu9001 9mo agoIsn't JS the same? But seems like people tend to make a lot of exception types in Java with inheritance, which I think is overkill. Typically I'll only have a couple of exception types that my own code throws, like user error vs system error. If I want more detail than that, it goes into the exception payload rather than defining many different types of exceptions.