Skip to content
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

Mark feature-gated items in docs #55

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

geigerzaehler
Copy link

We’re making use of the doc(cfg(..)) attribute to mark items in the docs that are behind feature flags. The approach seems pretty standard and is, for example, followed by the futures-* and async_std crates.

To ensure this is tested we add an additional travis job for this. This also checks the broken_intra_doc_links lint. To pass, we fixed the links in the crate documentation in lib.rs.

We’re making use of the [`doc(cfg(..))`][1] attribute to mark items in
the docs that are behind feature flags. The approach seems pretty
standard and is, for example, followed by the `futures-*` and
`async_std` crates.

To ensure this is tested we add an additional travis job for this. This
also checks the [`broken_intra_doc_links`][2] lint. To pass, we fixed
the links in the crate documentation in `lib.rs`.

[1]: https://doc.rust-lang.org/rustdoc/unstable-features.html#documenting-platform-feature-specific-information
[2]: https://doc.rust-lang.org/rustdoc/lints.html#broken_intra_doc_links
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant