Methods are not shown for pub type that is imported from other crate

[hellow554]

Location

I searched for FatalError in the rustc docs: https://doc.rust-lang.org/nightly/nightly-rustc/?search=fatalerror
The first two results are the interesting ones: rustc_errors::FatalError and rustc_span::fatal_error::FatalError

When opening the rustc_span::fatal_error::FatalError page, the associated method raise is shown:

When opening the rustc_errors::FatalError, the method won't show up:

This looks like a bug to me, because you can call the public method through the public export, so that method should either be documented or a page forward should happen to the original struct.

[kadiwa4]

Judging by the linked example, this has been fixed.
@rustbot label: +E-needs-test

[fmease]

Triage 2024: Oof, it's quite hard to come up with an MCVE after the fact ^^'. That would've been useful for doing a bisection and for adding a regression test (or for checking if we already have a similar one).

I tried to reproduce it with nightly-2022-10-11 and nightly-2022-10-12 (based on the creation date of this issue and the fact that rustc's API docs get rebuilt 'nightly').

I tried a two file setup of the form:

// span.rs
pub mod fatal_error {
    pub struct FatalError;

    impl FatalError {
        pub fn raise(self) -> ! { loop {} }
    }
}

rustc +nightly-2022-10-12 span.rs --crate-type lib --edition 2021

// error.rs
pub use span::fatal_error::FatalError;

rustdoc +nightly-2022-10-12 error.rs --edition 2021 -Lcrate=. --extern span

[fmease]

I know that Guillaume fixed a bunch of reexport issues earlier this year and late last year but I'm not super sure how to proceed with this specific issue at this time.