Note to self: we can document exit codes by piggy backing off the ErrorKind enum. For HTTP services we can do something similar for exit codes, but we'd also need to separate the Error files. 1 for crate level errors, and one for HTTP related errors.
-
-
Show this thread
-
If this actually ends up working I think we should be mostly feature complete. Ergonomics aside (so much boilerplate!), the final missing piece in the error handling story would probably be retries &/ supervisors.
Show this thread
End of conversation
New conversation -
-
-
Working on a quick CLI app, and I think it's so cool that it's possible to look at all possible failure modes in the application :Dpic.twitter.com/GW0Fh7AOHc
Show this thread -
I mean: look how nice this is! An error occurred during testing, and we can trace down the reason of it all the way down! This is so much better than stack traces when you're tracking down exceptions. Perfectly to the point; so much less time spent debugging! :Dpic.twitter.com/SJvgS03JDi
Show this thread
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.