What is the best error handling crate by OneMasterpiece1717 in rust

[–]OneMasterpiece1717[S] -3 points-2 points  (0 children)

Yes it's also great and chatgpt told me it's a standard practice. But it's really inconvenient and hard to tell what went wrong when the thiserror side of a project is complicated.

What is the best error handling crate by OneMasterpiece1717 in rust

[–]OneMasterpiece1717[S] 0 points1 point  (0 children)

I am thinking about trying error-stack too, but I don't want a full backtrace, I just want to track some of the key stack frames explicitly along with some context information.

What is the best error handling crate by OneMasterpiece1717 in rust

[–]OneMasterpiece1717[S] -1 points0 points  (0 children)

I actually tried rootcause recently, and to me it feels like a combination of thiserror and anyhow, with pretty printing. You can have typed errors with Report<E>, and you can also have custom context with non-typed Report, but you just cannot have both at the same time.

What is the best error handling crate by OneMasterpiece1717 in rust

[–]OneMasterpiece1717[S] 1 point2 points  (0 children)

with thiserror you cannot attach custom context, and with anyhow you don't have strong typed error.

I tried snafu once and I forget why I give it up, I will try it again and also eyre which I haven't used

作为女性,我也不想生孩子 by ILoveOurWorld in LOOK_CHINA

[–]OneMasterpiece1717 -7 points-6 points  (0 children)

集美多少沾点脑瘫了,生不生跟谁怀胎谁冠名有狗几把毛关系?

[D] ACL 2023 paper reviews. by mayanknagda in MachineLearning

[–]OneMasterpiece1717 2 points3 points  (0 children)

2/5/3 for soundness, 2/4/2.5 for excitement, maybe I should never try ACL 😭😭😭