Enable v0.1 std-trait workaround for additional targets #169
+41
−26
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.
Fixes #168
The first commit cleans up how we handle our various helper modules (similar to what we did for
v0.2
), but does not make any functional changes.The second commit enables our
std::error::Error
implementations forwindows
,target_os = "fuchsia"
,target_os = "ios"
. These are the additionalwindows
andunix
targets we supported inv0.1.6
. We don't enable the workaround fortarget_arch = "wasm32"
as that would be a breaking change (from newer version) forno_std
wasm32
targets.Here is a history of when we've enabled
std::error::Error
implementations:v0.1.0
-v0.1.6
:std
feature on most targetsv0.1.7
-v0.1.8
:unix
targets that neededutil_libc
v0.1.9
-v0.1.10
:"std"
featurev0.1.11 - v0.1.15
v0.1.9
changes (as they were a breaking change)