Fix accidentally forced std/allocator on no_std #171
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.
The
cfg
config forstd
/ALLOCATOR
might be accidentally too permissive.Specifically, as it currently stands:
This code brings in
std
even if the featurestd
is not enabled (becauseany
would hold true if even one of the two conditions is true). Similarly, forALLOCATOR
.By changing it to
all
instead ofany
, it is only applicable for tests for non-std
configuration, which is what I believe the intention is here.