Hacker News Reader

Checked Exceptions are nothing but errors as values with some syntactic sugar for the most common use case (bubbling up the error).

Gos version of value errors is just micrometers ahead of C style error codes. In both cases you get told "there could be an error", the error is a value of one single type (error/int), and you have to manually find out which different errors this value could represent.

If you want to know what you're missing, check out Rusts error handling.

I love Rust error handling and wish it would have been the default in Go (too late to shoehorn it), but it has nothing to do with exceptions.

Panics can be values and errors don't have to be values in go?

I think you are missing up concepts here

I’m not talking about the underlying model, I’m talking about the control flow. What I mean is errors are explicit values belonging to the signature of the functions.

Madness.