“for most programmers, being able to ignore potential error states is the essential feature that they really desire from their languages.”
-
-
getting implementations done, but leave a very clear breadcrumb trail of the cases you skipped over. 2/2
-
or `except()` so you know where something failed with an error message.
-
once you go to production, yeah. unwrap() is a godsend for getting through the happy path.
-
If only every user only used happy code paths.
-
the alternative I prefer is to exclude unhappy paths by construction.
-
works when it works.
-
More often than not in my day-to-day data plumbing, at least.
-
if the error comes from state that isn't known at compile time (FS), this seems impossible.
- 9 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.