Rust

8136 readers

208 users here now

Welcome to the Rust community! This is a place to discuss about the Rust programming language.

Wormhole

!performance@programming.dev

Credits

The icon is a modified version of the official rust logo (changing the colors to a gradient and black background)

founded 3 years ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

EdTheLegendary@programming.dev

torcherist@programming.dev

Error Handling in Rust vs. Exceptions in other languages (slicker.me)

submitted 1 month ago by monica_b1998@lemmy.world to c/rust@programming.dev

23 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] SorteKanin@feddit.dk 4 points 1 month ago* (last edited 1 month ago) (1 children)

catch_unwind [...] does not guarantee the program is in a consistent state afterward, since Drop impls may have run partway through.

Wait, what? Any more details about this, I've never heard about that before. Partially run Drop impls sounds like a big potential for undefined behavior, how could catch_unwind possibly cause that?

EDIT: The more I read this article, the more AI-generated it looks and so I'm sort of wondering if the above quote is just complete bogus.

[–] KillTheMule@programming.dev 3 points 1 month ago

Wait, what? Any more details about this, I’ve never heard about that before. Partially run Drop impls sounds like a big potential for undefined behavior, how could catch_unwind possibly cause that?

Yeah, no, I don't think this is true. It's the reason a double panic will cause an abort. The docs do recommend against using this for general error recovery, but there's no mention of any possibillity of inconsistent state.