Re:Another go at the Next Big Language
by yanatan16 on Sunday September 02, 2012 @10:31PM
(#4468906)
You don't want a language to force error handling on you. Error handling is different in every case. Go only tries to force you to deal with errors instead of allowing you to ignore them until an exception is thrown. There is never going to be an all-purpose error handling answer. Its just a matter of deciding where your error handling code is placed.
[ Parent
| on HN ]
Re:Another go at the Next Big Language
by eckyptang on Monday September 03, 2012 @02:59AM
(#4469400)
This is the most sensible comment I've ever seen on error handling and one I agree with entirely.
When designing the architecture for an application, error handling is actually the first thing I look at. It's different depending on where it is, who needs to handle it and the context it applies in (technical or business domain). There is no "one size fits all" solution.