rustdoc: Tracking issue for #[doc(cfg)] and automatically documented #[cfg]s #43781
Description
This is a tracking issue for RFC 3631.
The feature gate for this doc_cfg (doc_cfg_hide and doc_auto_cfg were removed in favor this overarching one).
Part of #1998.
Note
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.
Instead, open a dedicated issue for the specific matter or post in the #t-rustdoc Zulip channel.
Discussion comments will get marked as off-topic or deleted.
Repeated discussions on the tracking issue may lead to the tracking issue getting locked.
Steps
- Experimental implementation
- Adjust documentation
- Write an RFC
- Update implementation to match RFC
- Check performance impact on big crates
- Stabilization PR (see instructions on forge):
Implementation history
Metadata
Metadata
Assignees
Labels
Area: Attributes (`#[…]`, `#![…]`)Area: `cfg` conditional compilationBlocker: Approved by a merged RFC and implemented but not stabilized.Blocker: Implemented in the nightly compiler and unstable.Category: An issue tracking the progress of sth. like the implementation of an RFC`#![feature(doc_auto_cfg)]``#![feature(doc_cfg)]`Status: The implementation is "complete" but it needs time to bake.Relevant to the rustdoc team, which will review and decide on the PR/issue.
Type
Projects
Status