rust/tests/rustdoc/doc-hidden-private-67851-hidden.rs

//@ compile-flags: -Zunstable-options --document-hidden-items
// https://github.com/rust-lang/rust/issues/67851
#![crate_name="foo"]

//@ has foo/struct.Hidden.html
#[doc(hidden)]
pub struct Hidden;

//@ !has foo/struct.Private.html
struct Private;
[AUTO_GENERATED] Migrate compiletest to use `ui_test`-style `//@` directives 2024-02-22 06:10:29 -06:00			`//@ compile-flags: -Zunstable-options --document-hidden-items`
Add URL and crate_name to test cases 2024-04-06 16:41:09 -05:00			`// https://github.com/rust-lang/rust/issues/67851`
			`#![crate_name="foo"]`
Distinguish between private items and hidden items in rustdoc I believe rustdoc should not be conflating private items (visibility lower than `pub`) and hidden items (attribute `doc(hidden)`). This matters now that Cargo is passing --document-private-items by default for bin crates. In bin crates that rely on macros, intentionally hidden implementation details of the macros can overwhelm the actual useful internal API that one would want to document. This PR restores the strip-hidden pass when documenting private items, and introduces a separate unstable --document-hidden-items option to skip the strip-hidden pass. The two options are orthogonal to one another. 2020-01-04 12:58:32 -06:00
Update `tests/rustdoc` to new test syntax 2024-06-21 07:03:08 -05:00			`//@ has foo/struct.Hidden.html`
Distinguish between private items and hidden items in rustdoc I believe rustdoc should not be conflating private items (visibility lower than `pub`) and hidden items (attribute `doc(hidden)`). This matters now that Cargo is passing --document-private-items by default for bin crates. In bin crates that rely on macros, intentionally hidden implementation details of the macros can overwhelm the actual useful internal API that one would want to document. This PR restores the strip-hidden pass when documenting private items, and introduces a separate unstable --document-hidden-items option to skip the strip-hidden pass. The two options are orthogonal to one another. 2020-01-04 12:58:32 -06:00			`#[doc(hidden)]`
			`pub struct Hidden;`

Update `tests/rustdoc` to new test syntax 2024-06-21 07:03:08 -05:00			`//@ !has foo/struct.Private.html`
Distinguish between private items and hidden items in rustdoc I believe rustdoc should not be conflating private items (visibility lower than `pub`) and hidden items (attribute `doc(hidden)`). This matters now that Cargo is passing --document-private-items by default for bin crates. In bin crates that rely on macros, intentionally hidden implementation details of the macros can overwhelm the actual useful internal API that one would want to document. This PR restores the strip-hidden pass when documenting private items, and introduces a separate unstable --document-hidden-items option to skip the strip-hidden pass. The two options are orthogonal to one another. 2020-01-04 12:58:32 -06:00			`struct Private;`