cc/ @davidtolnay
-
-
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
Can you expand on how QoL has improved?
-
Multiple people have reached out about the improved readability of error messages. We interop with the standard trait now. We have a clean split between dynamic and structured error handling.
Kraj razgovora
Novi razgovor -
-
-
Honestly, I’m highly tempted to just drop back to std Error at this point. The number of time I’ve converted is getting a bit onerous.
-
std::error::Error is totally usable now! Maybe use `thiserror` to generate nice structured errors though.
Kraj razgovora
Novi razgovor -
-
-
Urg, this whole error debate again... Using just the std errors was good enough for me and I don't have to migrate once a year to a new preferred way to handle them. :)
-
Using std::error::Error is acceptable to me now! It wasn't in the past, but is good now. thiserror is a good choice for elegantly making those errors. anyhow is nice if you have dynamic errors. I don't feel this guidance is in conflict with your sentiment.
- Još 1 odgovor
Novi razgovor -
-
-
Is there a blog post written about this migration?
-
Nope, but I'm more than happy to answer any questions you may have
- Još 1 odgovor
Novi razgovor -
-
-
But literally everyone including you told me to use failure!
-
That was a while ago though! std::error::Error wasn't ready yet
- Još 5 drugih odgovora
Novi razgovor -
Č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.
Been known to wander around interesting parts of the planet.
Opinions my own, not my employers.
he/him 