rust/tests/rustdoc/internal.rs

//@ compile-flags: -Z force-unstable-if-unmarked

// Check that the unstable marker is not added for "rustc_private".

// @!matches internal/index.html \
//      '//*[@class="desc docblock-short"]/span[@class="stab unstable"]' \
//      ''
// @!matches internal/index.html \
//      '//*[@class="desc docblock-short"]/span[@class="stab internal"]' \
//      ''
// @matches - '//*[@class="desc docblock-short"]' 'Docs'

// @!has internal/struct.S.html '//*[@class="stab unstable"]' ''
// @!has internal/struct.S.html '//*[@class="stab internal"]' ''
/// Docs
pub struct S;

fn main() {}
display rustc_private APIs as "Internal" 2018-12-12 21:51:04 -06:00			`//@ compile-flags: -Z force-unstable-if-unmarked`

Don't render unstable for rustc docs As rustc is permanently unstable. So marking every items with unstable is essential useless. 2020-07-14 23:13:25 -05:00			`// Check that the unstable marker is not added for "rustc_private".`

rustdoc: Fix incorrect usage of `@!has` and `@!matches` `@!has` (and `@!matches`) with two arguments used to treat the second argument as a literal string of HTML code. Now, that feature has been renamed into `@!hasraw` (and `@!matchesraw`), and the arity-2 `@!has` version is an error. These uses thought the second argument was being treated as an XPath, as with the arity-3 version, but in fact was being treated as literal HTML. Because these were checking for the absence of the string, the tests silently did nothing -- an XPath string won't ever be showing up in the test's generated HTML! 2022-08-12 23:56:16 -05:00			`// @!matches internal/index.html \`
rustdoc: simplify DOM for `.item-table` This switches from using `<div>` to the more semantic `<ul>`, and using class names that rhyme with the classes the search results table uses. 2023-02-07 20:00:18 -06:00			`// '//*[@class="desc docblock-short"]/span[@class="stab unstable"]' \`
rustdoc: Fix incorrect usage of `@!has` and `@!matches` `@!has` (and `@!matches`) with two arguments used to treat the second argument as a literal string of HTML code. Now, that feature has been renamed into `@!hasraw` (and `@!matchesraw`), and the arity-2 `@!has` version is an error. These uses thought the second argument was being treated as an XPath, as with the arity-3 version, but in fact was being treated as literal HTML. Because these were checking for the absence of the string, the tests silently did nothing -- an XPath string won't ever be showing up in the test's generated HTML! 2022-08-12 23:56:16 -05:00			`// ''`
			`// @!matches internal/index.html \`
rustdoc: simplify DOM for `.item-table` This switches from using `<div>` to the more semantic `<ul>`, and using class names that rhyme with the classes the search results table uses. 2023-02-07 20:00:18 -06:00			`// '//*[@class="desc docblock-short"]/span[@class="stab internal"]' \`
rustdoc: Fix incorrect usage of `@!has` and `@!matches` `@!has` (and `@!matches`) with two arguments used to treat the second argument as a literal string of HTML code. Now, that feature has been renamed into `@!hasraw` (and `@!matchesraw`), and the arity-2 `@!has` version is an error. These uses thought the second argument was being treated as an XPath, as with the arity-3 version, but in fact was being treated as literal HTML. Because these were checking for the absence of the string, the tests silently did nothing -- an XPath string won't ever be showing up in the test's generated HTML! 2022-08-12 23:56:16 -05:00			`// ''`
rustdoc: simplify DOM for `.item-table` This switches from using `<div>` to the more semantic `<ul>`, and using class names that rhyme with the classes the search results table uses. 2023-02-07 20:00:18 -06:00			`// @matches - '//*[@class="desc docblock-short"]' 'Docs'`
rustdoc: wrap stability tags in colored spans 2019-01-14 09:02:27 -06:00
rustdoc: Fix incorrect usage of `@!has` and `@!matches` `@!has` (and `@!matches`) with two arguments used to treat the second argument as a literal string of HTML code. Now, that feature has been renamed into `@!hasraw` (and `@!matchesraw`), and the arity-2 `@!has` version is an error. These uses thought the second argument was being treated as an XPath, as with the arity-3 version, but in fact was being treated as literal HTML. Because these were checking for the absence of the string, the tests silently did nothing -- an XPath string won't ever be showing up in the test's generated HTML! 2022-08-12 23:56:16 -05:00			`// @!has internal/struct.S.html '//*[@class="stab unstable"]' ''`
			`// @!has internal/struct.S.html '//*[@class="stab internal"]' ''`
display rustc_private APIs as "Internal" 2018-12-12 21:51:04 -06:00			`/// Docs`
			`pub struct S;`

			`fn main() {}`