Don't let unstable-locales
imply the alloc
feature
#1307
Merged
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.
I hope that at some point we add support for parsing different locales (should not be all that hard). And that we can make the new formatting API work without
alloc
(proven to be possible in #1163).In both cases it does not make much sense for the
unstable-locales
feature to imply thealloc
feature.This will break uses of chrono with
no-default-features
with theunstable-locales
feature, that happen to also depend onalloc
.I feel we are allowed to make this change because of the name unstable-locales.
Split out from #1163.