Export std error type so no_std data formats don't need a "std" feature #1620
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds
serde::ser::StdError
andserde::de::StdError
which are either a re-export ofstd::error::Error
(if "std" is enabled) or a new identical trait (otherwise).Serde's error traits
serde::ser::Error
andserde::de::Error
requirestd::error::Error
as a supertrait, but only when Serde is built with "std" enabled. Data formats that don't care about no_std support should generally provide their error types with astd::error::Error
impl directly:Data formats that do support no_std may either have a "std" feature of their own:
... or else provide the std Error impl unconditionally via Serde's re-export:
FYI @oli-obk, @cbeck88