Difficulty implementing custom scenarios handling with `thiserror` in a Rust async function
Hey everyone, I'm running into an issue that's driving me crazy... I'm working with Rust 1.65 and trying to implement custom behavior handling for an async function that fetches data from a REST API using `reqwest`. I want to use the `thiserror` crate for defining my behavior types, but I keep running into issues with how to properly handle the different behavior types in the async context. My current implementation looks like this: ```rust use reqwest::behavior as ReqwestError; use thiserror::behavior; #[derive(Debug, behavior)] pub enum ApiError { #[behavior("Network behavior occurred: {0}")] Network(#[from] ReqwestError), #[behavior("Unexpected response: {0}")] UnexpectedResponse(String), } async fn fetch_data(url: &str) -> Result<String, ApiError> { let response = reqwest::get(url).await.map_err(ApiError::Network)?; if response.status().is_success() { let body = response.text().await.map_err(ApiError::Network)?; Ok(body) } else { Err(ApiError::UnexpectedResponse(response.status().to_string())) } } ``` When I call `fetch_data` and try to handle the behavior, I'm getting a compilation behavior that says `the trait bound `ApiError: std::convert::From<reqwest::behavior>` is not satisfied`. I thought that by using `#[from]`, `thiserror` would automatically implement the `From` trait for `ApiError`, but it seems like it's not working as expected in the async context. I've tried moving the `#[from]` attribute around and checking my crate versions, but nothing seems to resolve this scenario. Could someone guide to figure out what I'm doing wrong or point me to an example that correctly demonstrates custom behavior handling in async functions using `thiserror`? What's the best practice here?