Driveby feedback as requested. Big +1 for thiserror, I'm a huge fan of that crate and hope that it ends up as an inspiration for an error derive that eventually ends up in std. The from box stuff looks solid but I feel like from(unboxed) better reflects what it's doing.
-
-
-
I'm not sure I like the from-unwrap stuff. It seems a little counter intuitive to me and took a bit to understand. I'm not sure how I feel about implicitly discarding one step in an error causation chain (that's what it does right?) but I also don't know tikv's source well.
- Još 3 druga odgovora
Novi razgovor -
-
-
I switched our work codebase over to a combination of anyhow + thiserror recently (from error-chain) and have been pretty happy with it so far! We could probably do without thiserror even but it's nice to have some explicitly named errors.
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
Switched whole codebase (multiple binaries and libraries) to use exclusively `thiserror`, but we also are obsessively using structured errors & enums and therefore our error types are not too large. In progress of writing up a blog post about it too.
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.