@rustlang peeps: I want to write a blanket trait impl of From<T> for Type where T implements Trait, and Type also implements Trait, but where T and Type are not the same type. Is there a way in trait bounds to specify effectively "T: !Type" to avoid conflict w/ `From<T> for T`?
-
-
True. I am going to actually create a specific AWS errorkind and handle them directly. Thanks for the help.
-
Will also keep the dual trait idea in mind for a suitable use case. I was about to go down that route (impl a new owned trait for each error type, and bind on that trait) until I decided against.
End of conversation
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.