-
Notifications
You must be signed in to change notification settings - Fork 12.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add chapter for re-exports in the rustdoc book #109456
Add chapter for re-exports in the rustdoc book #109456
Conversation
pub use self::public_mod::Public; | ||
``` | ||
|
||
Likewise, if an item inherits has `#[doc(hidden)]` or inherits it (from any of its parents), it |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Likewise, if an item inherits has `#[doc(hidden)]` or inherits it (from any of its parents), it | |
Likewise, if an item has `#[doc(hidden)]` or inherits it (from any of its parents), it |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We probably want to specifically mention how attribute merging works:
Attributes
When an item is inlined, its doc comments and most of its attributes will be inlined along with it.
Attribute Inlined? Notes #[doc=""]
Yes Intra-doc links are resolved relative to where the doc comment is defined ( ///
is syntax sugar for doc string attributes).#[doc(cfg(..))]
Yes #[deprecated]
Yes Intra-doc links are resolved relative to where the description is defined. #[doc(alias="")]
No #[doc(hidden)]
No Hiding an item interacts with inlining the same way making an item private does. All other attributes are inherited when inlined, so that the documentation matches the behavior if the inlined item was directly defined at the spot where it's shown.
The job Click to see the possible cause of the failure (guessed by this bot)
|
I leave it as a draft for now because I prefer for #109449 to be solved first.
@petrochenkov is there something not covered in here that you might need?
r? @notriddle