I like that errors stay in the flow of control. No "Exception"s leaping up thru multiple levels of call stack. Instead the plan is: 1) see the error, 2) "%w" th

I like that errors stay in the flow of control. No "Exception"s leaping up thru multiple levels of call stack. Instead the plan is: 1) see the error, 2) "%w" the error, 3) kick it upstairs, 4) Mission Accomplished. And at some level, some piece of code will grab the bull by the horns and wrestle it to the ground. All in all, errors-as-values is a calm way to deal with unhappy code paths. A clear renunciation of longjump. (Golang system-originated panics are excepted from this gloss, but they are defined quite narrowly, and ofc catchable.)