mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
e1eaa2d5d4
rust/tests/rustdoc/duplicate-cfg.rs

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

54 lines
2.0 KiB
Rust
Raw Normal View History

Remove potential cfgs duplicates
2019-12-03 11:07:00 -06:00
#![crate_name = "foo"]
#![feature(doc_cfg)]
Add long cfg description to tooltip on short description
2020-08-18 15:19:02 -05:00
// @has 'foo/index.html'
rustdoc: remove mostly-unused CSS classes import/module-item
2023-01-26 13:50:14 -06:00
// @matches '-' '//*[@class="item-left"]//*[@class="stab portability"]' '^sync$'
// @has '-' '//*[@class="item-left"]//*[@class="stab portability"]/@title' 'Available on crate feature `sync` only'
Add long cfg description to tooltip on short description
2020-08-18 15:19:02 -05:00
rustdoc: Remove more `#[doc(cfg(..))]` duplicates
2020-01-06 17:57:02 -06:00
// @has 'foo/struct.Foo.html'
Add long cfg description to tooltip on short description
2020-08-18 15:19:02 -05:00
// @has '-' '//*[@class="stab portability"]' 'sync'
Remove potential cfgs duplicates
2019-12-03 11:07:00 -06:00
#[doc(cfg(feature = "sync"))]
#[doc(cfg(feature = "sync"))]
Add test for item-table with resize to mobile
2021-06-24 07:30:01 -05:00
/// my feature sync struct
Remove potential cfgs duplicates
2019-12-03 11:07:00 -06:00
pub struct Foo;
Add long cfg description to tooltip on short description
2020-08-18 15:19:02 -05:00
// @has 'foo/bar/index.html'
clarify doc(cfg) wording The current "This is supported" wording implies that it's possible to still use the item on other configurations, but in an unsupported way. Changing this to "Available" removes this ambiguity.
2022-04-14 18:03:56 -05:00
// @has '-' '//*[@class="stab portability"]' 'Available on crate feature sync only.'
Remove potential cfgs duplicates
2019-12-03 11:07:00 -06:00
#[doc(cfg(feature = "sync"))]
pub mod bar {
Simplify doc-cfg rendering based on the current context For sub-items on a page don't show cfg that has already been rendered on a parent item. At its simplest this means not showing anything that is shown in the portability message at the top of the page, but also for things like fields of an enum variant if that variant itself is cfg-gated then don't repeat those cfg on each field of the variant. This does not touch trait implementation rendering, as that is more complex and there are existing issues around how it deals with doc-cfg that need to be fixed first.
2020-10-06 13:48:01 -05:00
// @has 'foo/bar/struct.Bar.html'
clarify doc(cfg) wording The current "This is supported" wording implies that it's possible to still use the item on other configurations, but in an unsupported way. Changing this to "Available" removes this ambiguity.
2022-04-14 18:03:56 -05:00
// @has '-' '//*[@class="stab portability"]' 'Available on crate feature sync only.'
Remove potential cfgs duplicates
2019-12-03 11:07:00 -06:00
#[doc(cfg(feature = "sync"))]
pub struct Bar;
}
rustdoc: Remove more `#[doc(cfg(..))]` duplicates
2020-01-06 17:57:02 -06:00
Add long cfg description to tooltip on short description
2020-08-18 15:19:02 -05:00
// @has 'foo/baz/index.html'
clarify doc(cfg) wording The current "This is supported" wording implies that it's possible to still use the item on other configurations, but in an unsupported way. Changing this to "Available" removes this ambiguity.
2022-04-14 18:03:56 -05:00
// @has '-' '//*[@class="stab portability"]' 'Available on crate features sync and send only.'
rustdoc: Remove more `#[doc(cfg(..))]` duplicates
2020-01-06 17:57:02 -06:00
#[doc(cfg(all(feature = "sync", feature = "send")))]
pub mod baz {
Simplify doc-cfg rendering based on the current context For sub-items on a page don't show cfg that has already been rendered on a parent item. At its simplest this means not showing anything that is shown in the portability message at the top of the page, but also for things like fields of an enum variant if that variant itself is cfg-gated then don't repeat those cfg on each field of the variant. This does not touch trait implementation rendering, as that is more complex and there are existing issues around how it deals with doc-cfg that need to be fixed first.
2020-10-06 13:48:01 -05:00
// @has 'foo/baz/struct.Baz.html'
clarify doc(cfg) wording The current "This is supported" wording implies that it's possible to still use the item on other configurations, but in an unsupported way. Changing this to "Available" removes this ambiguity.
2022-04-14 18:03:56 -05:00
// @has '-' '//*[@class="stab portability"]' 'Available on crate features sync and send only.'
rustdoc: Remove more `#[doc(cfg(..))]` duplicates
2020-01-06 17:57:02 -06:00
#[doc(cfg(feature = "sync"))]
pub struct Baz;
}
Simplify doc-cfg rendering based on the current context For sub-items on a page don't show cfg that has already been rendered on a parent item. At its simplest this means not showing anything that is shown in the portability message at the top of the page, but also for things like fields of an enum variant if that variant itself is cfg-gated then don't repeat those cfg on each field of the variant. This does not touch trait implementation rendering, as that is more complex and there are existing issues around how it deals with doc-cfg that need to be fixed first.
2020-10-06 13:48:01 -05:00
// @has 'foo/qux/index.html'
clarify doc(cfg) wording The current "This is supported" wording implies that it's possible to still use the item on other configurations, but in an unsupported way. Changing this to "Available" removes this ambiguity.
2022-04-14 18:03:56 -05:00
// @has '-' '//*[@class="stab portability"]' 'Available on crate feature sync only.'
rustdoc: Remove more `#[doc(cfg(..))]` duplicates
2020-01-06 17:57:02 -06:00
#[doc(cfg(feature = "sync"))]
pub mod qux {
Simplify doc-cfg rendering based on the current context For sub-items on a page don't show cfg that has already been rendered on a parent item. At its simplest this means not showing anything that is shown in the portability message at the top of the page, but also for things like fields of an enum variant if that variant itself is cfg-gated then don't repeat those cfg on each field of the variant. This does not touch trait implementation rendering, as that is more complex and there are existing issues around how it deals with doc-cfg that need to be fixed first.
2020-10-06 13:48:01 -05:00
// @has 'foo/qux/struct.Qux.html'
clarify doc(cfg) wording The current "This is supported" wording implies that it's possible to still use the item on other configurations, but in an unsupported way. Changing this to "Available" removes this ambiguity.
2022-04-14 18:03:56 -05:00
// @has '-' '//*[@class="stab portability"]' 'Available on crate features sync and send only.'
rustdoc: Remove more `#[doc(cfg(..))]` duplicates
2020-01-06 17:57:02 -06:00
#[doc(cfg(all(feature = "sync", feature = "send")))]
pub struct Qux;
}
Add long cfg description to tooltip on short description
2020-08-18 15:19:02 -05:00
// @has 'foo/quux/index.html'
clarify doc(cfg) wording The current "This is supported" wording implies that it's possible to still use the item on other configurations, but in an unsupported way. Changing this to "Available" removes this ambiguity.
2022-04-14 18:03:56 -05:00
// @has '-' '//*[@class="stab portability"]' 'Available on crate feature sync and crate feature send and foo only.'
rustdoc: Remove more `#[doc(cfg(..))]` duplicates
2020-01-06 17:57:02 -06:00
#[doc(cfg(all(feature = "sync", feature = "send", foo)))]
pub mod quux {
Simplify doc-cfg rendering based on the current context For sub-items on a page don't show cfg that has already been rendered on a parent item. At its simplest this means not showing anything that is shown in the portability message at the top of the page, but also for things like fields of an enum variant if that variant itself is cfg-gated then don't repeat those cfg on each field of the variant. This does not touch trait implementation rendering, as that is more complex and there are existing issues around how it deals with doc-cfg that need to be fixed first.
2020-10-06 13:48:01 -05:00
// @has 'foo/quux/struct.Quux.html'
clarify doc(cfg) wording The current "This is supported" wording implies that it's possible to still use the item on other configurations, but in an unsupported way. Changing this to "Available" removes this ambiguity.
2022-04-14 18:03:56 -05:00
// @has '-' '//*[@class="stab portability"]' 'Available on crate feature sync and crate feature send and foo and bar only.'
rustdoc: Remove more `#[doc(cfg(..))]` duplicates
2020-01-06 17:57:02 -06:00
#[doc(cfg(all(feature = "send", feature = "sync", bar)))]
pub struct Quux;
}
Reference in New Issue Copy Permalink