Tracking Issue for #![feature(doc_primitive)]
#88070
Labels
C-tracking-issue
Category: An issue tracking the progress of sth. like the implementation of an RFC
requires-nightly
This issue requires a nightly compiler in some way.
T-rustdoc
Relevant to the rustdoc team, which will review and decide on the PR/issue.
This is a tracking issue for using
#[doc(primitive)]
.The feature gate for the issue is
#![feature(doc_primitive)]
.This feature is not meant to ever become stable. It is an implementation detail of the standard library.
Due to an oversight when releasing Rust 1.0, this could previously be used without a feature gate. That was a bug: this feature is not useful to anyone other than the standard library, and the behavior when multiple crates use
doc(primitive)
at once is unspecified (see "Breaking changes to doc(primitive)" in #87073). To avoid needlessly breaking crates, anyone usingdoc(primitive)
without a feature gate will get a future-incompat warning instead of a hard error.#[doc(primitive)]
still has an effect even without the feature gate, but the behavior is still unspecified when more than one crate has the sameprimitive
attribute. Once #87073 is merged andcore
starts documenting all primitives, it will be completely unspecified whether the new documentation is used or not.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
doc(primitive)
#87050Unresolved Questions
Does this need an edition to become a hard error? Crater hasn't found any crates using this attribute: #87050 (comment)
The text was updated successfully, but these errors were encountered: