about summary refs log tree commit diff
path: root/src/test/rustdoc/duplicate-cfg.rs
AgeCommit message (Collapse)AuthorLines
2023-01-11Move /src/test to /testsAlbert Larsan-53/+0
2022-04-14clarify doc(cfg) wordingAndy Russell-9/+9
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.
2021-06-28Add test for item-table with resize to mobileStefan Schindler-2/+3
2021-06-24Migrate from custom elements to divs with classes to be compatible with safariStefan Schindler-2/+2
2021-06-24Implement Desktop and Mobile version with gridlayoutStefan Schindler-2/+2
* implement sans-serif #85621
2021-04-03Remove redundant `ignore-tidy-linelength` annotationsSimon Jakobi-2/+0
This is step 2 towards fixing #77548. In the codegen and codegen-units test suites, the `//` comment markers were kept in order not to affect any source locations. This is because these tests cannot be automatically `--bless`ed.
2020-10-07Simplify doc-cfg rendering based on the current contextWim Looman-15/+11
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-08-18Add long cfg description to tooltip on short descriptionWim Looman-1/+17
2020-08-09Render longhand multiple crate/target features nicerWim Looman-2/+2
2020-08-09Improve rendering of crate features via doc(cfg)Wim Looman-5/+5
2020-01-06rustdoc: Remove more `#[doc(cfg(..))]` duplicatesOliver Middleton-3/+30
2019-12-04Remove potential cfgs duplicatesGuillaume Gomez-0/+15