You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a tracking issue for the RFC "3239" (rust-lang/rfcs#3239).
The feature gate for the issue is #![feature(cfg_target)].
About tracking issues
Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.
How do we ensure a project does not miss configurations similar to the ones
being #[cfg]-ed against with this feature? Perhaps this should be added as a
Clippy lint that's off by default.
Implementation history
The text was updated successfully, but these errors were encountered:
RFC3239: Implement `cfg(target)` - Part 2
This pull-request implements the compact `cfg(target(..))` part of [RFC 3239](rust-lang#96901).
I recommend reviewing this PR on a per commit basics, because of some moving parts.
cc `@GuillaumeGomez`
r? `@petrochenkov`
This is a tracking issue for the RFC "3239" (rust-lang/rfcs#3239).
The feature gate for the issue is
#![feature(cfg_target)]
.About tracking issues
Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.
Steps
cfg(target)
- Part 1 #96909 and RFC3239: Implementcfg(target)
- Part 2 #96913)Unresolved Questions
being
#[cfg]
-ed against with this feature? Perhaps this should be added as aClippy lint that's off by default.
Implementation history
The text was updated successfully, but these errors were encountered: