In terms of how it actually fits into Rust, you want to use anyhow for application code. If you’re writing a library, then anyhow is a no-go, because users cannot match on different error classes with it. (Much like you would want custom exception classes, so that users can catch them in different catch branches and handle them differently.)
Every so often, you will also need matchable error classes within your application code, then you would have to replace anyhow with a custom error type there, too, of course.
I will also say, IMHO it is fine to use anyhow even while you’re learning Rust. It is so easy that you kind of skip learning error handling, which you will need to learn at some point, but you can still do that when you actually need it.
You can use the
anyhowcrate for something quite similar to exceptions: https://crates.io/crates/anyhowIn terms of how it actually fits into Rust, you want to use
anyhowfor application code. If you’re writing a library, thenanyhowis a no-go, because users cannot match on different error classes with it. (Much like you would want custom exception classes, so that users can catch them in different catch branches and handle them differently.)Every so often, you will also need matchable error classes within your application code, then you would have to replace
anyhowwith a custom error type there, too, of course.I will also say, IMHO it is fine to use
anyhoweven while you’re learning Rust. It is so easy that you kind of skip learning error handling, which you will need to learn at some point, but you can still do that when you actually need it.