2 ms·
I vote no on this proposal. Go error handling should remain simple, like the language. These are all tools, just pick the one you like and stop trying to make
by sigmonsays 2y ago
I vote no on this proposal.
Go error handling should remain simple, like the language.
These are all tools, just pick the one you like and stop trying to make them like others.
- echelon 2y ago> These are all tools, just pick the one you like and stop trying to make them like others. I'm not so sure I agree with that. I'm glad Rust continues to evolve at a healthy pace and pick up new syntactic features. Boilerplate is a sin against the brain. As long as you don't pay it down with increased cognitive complexity, it should be eliminated at all costs. Error handling is such an essential feature of problem solving that this should be one of the highest priorities for a language to get right. It should be so simple and elegant that you can bash it out in a few tokens, and almost impossible to get wrong. I think Go would be a much better language if it took this to task. I reach for Rust for out of domain problems because it's so expressive and intentional and safe and concise.
- eweise 2y agoBy that logic, Go shouldn't have generics but they've added a lot of value to our codebase.
- nonethewiser 2y agoGo is an incomplete language masquerading as a simple one.
- pjmlp 2y agoC should not care for safety, there are tools, pick the one you like....