Rustdoc fails to follow path after re-export.

[gyscos]

When re-exporting modules from another crate, documentation for this crate does not follow rust paths correctly.

A simple workspace to showcase the issue:

• A foo crate, with a foo module and a Foo struct in this module. The foo module has documentation linking to the Foo struct.
• A bar crate which depends on foo with the line pub use foo::*;
  From there, compiling documentation will:
• For the crate foo, correctly resolve the Foo link.
• For the crate bar, incorrectly resolve the link in the re-exported foo module.

# foo/src/lib.rs
pub mod foo {
    //! A mod.
    //!
    //! See [`Foo`]

    /// Some struct
    pub struct Foo;
}

# bar/src/lib.rs
pub use ::foo::*;

Here is a screenshot from the doc page for the foo module from the foo crate:

And here is the documentation for the foo module re-exported in the bar crate:

Here is a zip with the entire workspace ready to compile: rustdoc example.zip

I also tried using self::Foo, crate::foo::Foo, for the same result.

Apart from this simple example, this can happen with "facade" crates that re-export all or a subset of an other crate, and expect documentation to transparently work.

[ehuss]

This appears to be a duplicate of #65983.

[gyscos]

Arf, missed that, sorry!
The source post from #65983 looks more complex though, with [Baz] expected to point back to the source, though that may be just a superficial difference.

[gyscos]

Actually in my case I'd be very much fine with local resolution, pointing to the re-exported item as long as the module structure is the same.