Separate cfg-target-has-atomic feature #1442
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 intention here is that
nightlybecomes a marker feature for opting in to features that use unstable features, but by itself it doesn't activate any extra unstable features; users then activate the specificnightlyfeatures they need (e.g. #1438 for another nightly feature) . This avoids unnecessary breakage on downstream crates, e.g. iffeature(cfg_target_has_atomic)changes in some way we don't want to break crates that are only usingdefault-features = false, features = ["nightly", "alloc"].(this is sort of future proofing for things that will not be stable before the core traits can be released on stable, it doesn't mean much yet, but something like this will be necessary in the future)