rust/tests/rustdoc/issue-61592.rs

//@ aux-build:issue-61592.rs

extern crate foo;

// @has issue_61592/index.html
// @has - '//a[@href="#reexports"]' 'Re-exports'
// @has - '//code' 'pub use foo::FooTrait as _;'
// @!has - '//a[@href="trait._.html"]' ''
pub use foo::FooTrait as _;

// @has issue_61592/index.html
// @has - '//a[@href="#reexports"]' 'Re-exports'
// @has - '//code' 'pub use foo::FooStruct as _;'
// @!has - '//a[@href="struct._.html"]' ''
pub use foo::FooStruct as _;
Rustdoc render public underscore_imports as Re-exports Fixes #61592 2020-12-31 09:07:51 +00:00			`//@ aux-build:issue-61592.rs`

			`extern crate foo;`

			`// @has issue_61592/index.html`
			`// @has - '//a[@href="#reexports"]' 'Re-exports'`
			`// @has - '//code' 'pub use foo::FooTrait as _;'`
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-13 04:56:16 +00:00			`// @!has - '//a[@href="trait._.html"]' ''`
Rustdoc render public underscore_imports as Re-exports Fixes #61592 2020-12-31 09:07:51 +00:00			`pub use foo::FooTrait as _;`

			`// @has issue_61592/index.html`
			`// @has - '//a[@href="#reexports"]' 'Re-exports'`
			`// @has - '//code' 'pub use foo::FooStruct as _;'`
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-13 04:56:16 +00:00			`// @!has - '//a[@href="struct._.html"]' ''`
Rustdoc render public underscore_imports as Re-exports Fixes #61592 2020-12-31 09:07:51 +00:00			`pub use foo::FooStruct as _;`