I want to define a tripartite `Result` type which represents success, expected failure and unexpected failure (not for the first time I've tried but I have union types now!). It would be nice if I could find three equal-length words which convey these concepts. Which do you like?
-
The last one doesn't necessarily mean "fatal", as it might be recoverable or diagnosable. It's just "some exception that wasn't expected".
-
-
on recovering from unexpected error I have my doubts, how to manage unexpected result? except if you can restart the whole thing, like using retry policies..I don't know..maybe 3 types are not enough? you need expected, recoverable and unrecoverable error?
-
Maybe "unexpected" isn't the right word, exactly. "Unanticipated" might be better, in the sense that it would be a non-fatal exception that hasn't been specially handled, but any production app should probably handle it as an "unknown error" *somewhere*.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.