-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
Update documentation for doc_cfg feature #92818
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -84,6 +84,39 @@ in documentation. | |
`#![feature(doc_cfg)]` feature gate. For more information, see [its chapter in the Unstable | ||
Book][unstable-doc-cfg] and [its tracking issue][issue-doc-cfg]. | ||
|
||
### `doc_auto_cfg`: Automatically generate `#[doc(cfg)]` | ||
|
||
`doc_auto_cfg` is an extension to the `#[doc(cfg)]` feature. With it, you don't need to add | ||
`#[doc(cfg(...)]` anymore unless you want to override the default behaviour. So if we take the | ||
previous source code: | ||
|
||
```rust | ||
#![feature(doc_auto_cfg)] | ||
|
||
/// Token struct that can only be used on Windows. | ||
#[cfg(any(windows, doc))] | ||
pub struct WindowsToken; | ||
|
||
/// Token struct that can only be used on Unix. | ||
#[cfg(any(unix, doc))] | ||
pub struct UnixToken; | ||
|
||
/// Token struct that is only available with the `serde` feature | ||
#[cfg(feature = "serde")] | ||
#[derive(serde::Deserialize)] | ||
pub struct SerdeToken; | ||
``` | ||
|
||
It'll render almost the same, the difference being that `doc` will also be displayed. To fix this, | ||
you can use `doc_cfg_hide`: | ||
Comment on lines
+110
to
+111
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Not a comment about the docs, but shouldn't hiding There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Once #92856 is merged, it'll be pretty easy to ignore it as well. |
||
|
||
```rust | ||
#![feature(doc_cfg_hide)] | ||
#![doc(cfg_hide(doc))] | ||
``` | ||
|
||
And `doc` won't show up anymore! | ||
|
||
[cfg-doc]: ./advanced-features.md | ||
[unstable-doc-cfg]: ../unstable-book/language-features/doc-cfg.html | ||
[issue-doc-cfg]: https://github.com/rust-lang/rust/issues/43781 | ||
|
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
I think we should maybe put
doc_auto_cfg
in its own section (perhaps called#![feature(doc_auto_cfg)]
or something like that). It's kind of a freestanding feature—i.e., you can use it without usingdoc_cfg
.Make sure to change "An extension to this feature" to "An extension to
doc_cfg
".