Skip to content

rustdoc: Tracking issue for #[doc(cfg)] and automatically documented #[cfg]s #43781

Description

@kennytm

View all comments

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

Open issues

Unresolved questions

Resolved questions

Implementation history

Metadata

Metadata

Labels

A-attributesArea: Attributes (`#[…]`, `#![…]`)A-cfgArea: `cfg` conditional compilationB-RFC-implementedBlocker: Approved by a merged RFC and implemented but not stabilized.B-unstableBlocker: Implemented in the nightly compiler and unstable.C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCF-doc_cfg`#![feature(doc_cfg)]`S-tracking-needs-to-bakeStatus: The implementation is "complete" but it needs time to bake.T-rustdocRelevant to the rustdoc team, which will review and decide on the PR/issue.

Type

No type

Fields

No fields configured for issues without a type.

Projects

Status
Rejected/Not lang

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions