News for hackers. Stuff that matters.
Re:Declined Proposal: A built-in Go error check function, “try” by stcredzero on Wednesday July 17, 2019 @02:25PM (#20462549)
In some contexts, exceptions are just cleaner and easier.

Definitely. The question is, are the benefits in those contexts worth the cost of the potential abuses? As a codebase and company get larger and larger, the higher the probability that a problem will get into the codebase.

There is an analogy here with C++ templates and with method_missing meta-programming. There are some contexts where they make things a lot easier. However, in a large codebase, the probability that some programmer, somewhere is going to cause a costly problem with a bit of nifty overreach goes up and up.

Re:Declined Proposal: A built-in Go error check function, “try” by philwelch on Wednesday July 17, 2019 @10:43PM (#20466238)
While true, HTTP services in particular are a very, very common context.
Re:Declined Proposal: A built-in Go error check function, “try” by mikeschinkel on Friday July 19, 2019 @03:20PM (#20481654)
Then use panic() and recover() for that special type of use-case. Just as easy as exception handling.
Re:Declined Proposal: A built-in Go error check function, “try” by philwelch on Sunday July 21, 2019 @08:41PM (#20494639)
That's just exception handling with extra steps! ;)