|
|
|
|
|
|
by noisy_boy
459 days ago
|
|
|
I am not questioning it's effectiveness. I have written Go code that is chugging along without issues in Production. My point is ergonomics and effectiveness are not mutually exclusive - hence the example of Rust's ? operator - effective and ergonomic (Rust also has issues with difficult to read lifetime+trait annotations). The sad part is that people have been talking about this for years but Go team stubbornly refuses to make error handling more ergonomic. |
|
|
It is, but it's also subtle, and if you want branches (especially sad-path branches) to be explicit, that's not a good thing.