What’s the best argument to made made in favor of ... untyped errors in strongly typed languages?
-
You can mark an enum as non-exhaustive, which requires any `match`es outside the crate to have a default branch
For errors that's pretty much always what you'd do anyway, since if consumers care about any of your error variants it's probably only only one or two
-
-
Nice, swift enums have the same functionality. However, at that point it seems to me the specific error type isn't doing much for your clients
-
Depends on the context. Diesel has an error variant for "this query was expected to return 1 or more rows, but zero were returned" for example which is commonly handled. Really the point is more than if your consumers can recover from a specific case, don't take the choice away
- 4 more replies
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.