So I guess the follow up question here is: why do you all still use std::error?https://twitter.com/mitsuhiko/status/987234121117261824 …
-
-
Replying to @mitsuhiko @rustlang
Fail is good, but Sync requirement is annoying
1 reply 0 retweets 1 like -
What do you do with your errors that they are not sync?
2 replies 0 retweets 3 likes -
Replying to @mitsuhiko @rustlang
Sometimes I need to pass some data that represents error and data might be !Sync. Other example is actix-web, I’d like to give users ability to pass HttpResponse as error.
2 replies 0 retweets 1 like -
On the other hand because errors are so unconstrained in rust currently generic apis can’t do much with them. For instance they are entirely useless for sentry atm.
1 reply 0 retweets 0 likes -
Replying to @mitsuhiko @rustlang
But Fail is Send + Sync. So user would be able to send ResponseFail to different thread
1 reply 0 retweets 0 likes -
That’s fine
1 reply 0 retweets 0 likes
Replying to @mitsuhiko @rustlang
I am not so sure, because I use Rc and per thread objects pool
10:42 AM - 20 Apr 2018
0 replies
0 retweets
0 likes
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.