rust/tests/rustdoc/intra-doc/enum-struct-field.rs

#![crate_name = "foo"]

pub enum Foo {
    X {
        y: u8,
    }
}

/// Hello
///
/// I want [Foo::X::y].
pub fn foo() {}

// @has foo/fn.foo.html '//a/@href' 'enum.Foo.html#variant.X.field.y'
Add support for intra-doc link fields of enum variant 2019-11-24 16:27:52 +01:00			`#![crate_name = "foo"]`

			`pub enum Foo {`
			`X {`
			`y: u8,`
			`}`
			`}`

			`/// Hello`
			`///`
			`/// I want [Foo::X::y].`
			`pub fn foo() {}`

rustdoc: use more precise relative URLS Instead of using a depth counter and adding "../" to get to the top, this commit makes rustdoc actually compare the path of what it's linking from to the path that it's linking to. This makes the resulting HTML shorter. Here's a comparison of one of the largest (non-source) files in the Rust standard library docs (about 4% improvement before gzipping). $ wc -c struct.Wrapping.old.html struct.Wrapping.new.html 2387389 struct.Wrapping.old.html 2298538 struct.Wrapping.new.html Most if it can be efficiently gzipped away. $ wc -c struct.Wrapping.old.html.gz struct.Wrapping.new.html.gz 70679 struct.Wrapping.old.html.gz 70050 struct.Wrapping.new.html.gz But it also makes a difference in the final DOM size, reducing it from 91MiB to 82MiB. 2021-03-17 11:41:01 -07:00			`// @has foo/fn.foo.html '//a/@href' 'enum.Foo.html#variant.X.field.y'`