Rustdoc doesn't redirect links of uses of reexported items with inlined documentation

[huonw]

#[crate_id="reexports"];

pub use foo::{func, Type};

mod foo {
    /// Hi
    pub struct Type;

    /// Hello
    pub fn func(x: Type) {}
}

Rustdoc will generate the documentation for func and Type at the top level (i.e. reexports/struct.Type.html and reexports/fn.func.html), but the Type link in the signature of func points to reexports/foo/struct.Type.html, i.e. the non-inlined documentation.

[emberian]

cc me

[alexcrichton]

Hm, this is actually a really tough problem to solve. We could emit pages for reexports/foo/struct.Type.html which are a redirect to the "actual documentation", but knowing where that actual documentation is would be difficult. I think it could be done though.

[huonw]

Do we need a "resolve documentation paths" in rustdoc that goes through and maps nodeids (or whatever) to the appropriate paths?

[alexcrichton]

Hm, I think it may be better to avoid something like that. We could have a map of NodeId => path where the key is a node id of a private item that was re-exported to the value path. That way when the documentation page is generated for the key node id it would emit a redirect to the value path.

You could re-export a type in a few places and you'd end up linking to the last one, but it's certainly better than the current situation!

[chris-morgan]

This is seriously messing with the sync crate in which everything is public exports of the contents of private modules. As an example, DuplexStream: the link at the top of the page is right but the three links in the impl are wrong.