-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Psst, displaydoc works on structs and enums.
-
I mean, that's what it says doesn't it? (fixed it; oops oops, thanks for pointing it out!)
End of conversation
New conversation -
-
-
I feel like most of these crates push people into the big-ball-of-mud single top level error enum antipattern that makes handling errors of different severities at different call depths hard. It breaks pattern matching, which is really important in complex codebase
-
Downcasting is still supported which means you can don't lose the ability to pattern match. This was one of the bigger innovations of Failure, and motivated the deprecation of the causes API I'm favor of sources.
- 5 more replies
New conversation -
-
-
This was a fantastic read, thank you for putting this all together. It reminds me a lot of Nikos post a while back about the RFC process where instead of proposing and defending a solution everyone just explores the problem space together. Great work. Definitely bookmark worthy.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Thanks for writing this! Looks like a thorough and useful survey to drive the error handling story even further. I have a nagging feeling that there's still one pain poin that isn't mentioned, but I'm unable to reproduce good examples. It's about type conversion.
-
? Introduces a generic type conversion, and if you are doing another one before that, there are sometimes too many degrees of freedom for the inference to know what conversion is desired even though intuitively speaking, there's usually a clear "best choice".
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.