Rustdoc: Resolve to wrong mod when use glob reexport and non-glob reexport together

[longfangsong]

I'm trying to work on #83375, but found a related but not same bug:

I run rustdoc on this code:

// resolve.rs
pub mod sub {
    pub struct Item;

    /// sub::prelude
    pub mod prelude {
        pub use super::Item;

        pub fn describe() -> &'static str {
            "sub::prelude"
        }
    }
}

pub mod sub2 {
    pub struct Item;

    /// sub2::prelude
    pub mod prelude {
        pub use super::Item;
        pub fn describe() -> &'static str {
            "sub2::prelude"
        }
    }
}

#[doc(inline)]
pub use sub::*;

#[doc(inline)]
pub use sub2::prelude;

I expected to see this happen:
Only one prelude link exists and it resolves to sub2::prelude (if you do println!("{}", resolve::prelude::describe());, you'll get the output sub2::prelude)

Instead, this happened:

1. Similiar with Rustdoc: glob reexport may duplicate module #83375 described, there are two preludes here:

2. Moreover, if you visit either of the prelude links, it direct you to sub::prelude

Meta

rustdoc +local --version:

rustdoc 1.53.0-dev

Backtrace

NA

[longfangsong]

@rustbot label: +T-rustdoc -T-doc

[jyn514]

Duplicate of #83375 (but thanks for the report).

[jyn514]

The reason I consider them the same is they have the same cause: if there's already an item with that name in scope, rustdoc will use both that item and the glob re-export. Whether the item is a re-export or was defined in the current module shouldn't matter.

[jyn514]

rustdoc +local --version: rustdoc 1.53.0-dev

BTW, this isn't super helpful because the version is always the same - it's more helpful to link the commit you built from source.