What I dislike about *all* the dynamic `Error` strategies is that we can't have something that is both `From<E: Error>` and `impl Error` at the same time. ;__________;
I've had methods and enum variants with `E: Error` bounds that blew up when I changed one of my error types to `Box<dyn Error>`.
-
-
Instead of `where S::Error: Error`, it's become `where S::Error: Into<Box<dyn Error>>` everywhere, which is not as clear IMO.
-
Ah good call. I have some `type Error: StdError` associated types in Serde's traits that in hindsight should have been `type Error: Display + Debug` only. I would be curious to see an example of a function that really needs StdError bound on a generic parameter if you have one.
- 1 more reply
New conversation -
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.