Hacker News Reader

They leave you in about the same position as a programmer in a dynamic language.

The advantage of runtime exceptions over Go is that I will get a fatal crash and a stacktrace. I don't have computation proceeding in an undefined, difficult-to-debug way because I forgot to do `err != nil` somewhere (particularly for functions that only return err).

View on HN

Or someone will catch it and discard the result which is often often what occurs. For example, with java throw an exception in an executor task (an assertion failure for example). What do you think occurs?

Which happens in Go too. I've seen a lot of code that happily sails past functions which only return err, meaning the compiler never pipes up.

Don't get me wrong, though. I become grumpy when I see empty catch clauses. Or a logger figleaf.

Reply on news.ycombinator.com