Rustdoc doesn't show `repr` for a struct re-exported from another package

[nicholasbishop]

If you define a struct with an explicit repr(...) in one package, then pub use it in another package, rustdoc doesn't show the repr on the re-exported one.

Minimal repo showing this problem: https://github.com/nicholasbishop/pub-use-repr-doc-bug

In pkg1 you get:

But in pkg2 you get:

Meta

rustc --version --verbose:

rustc 1.69.0 (84c898d65 2023-04-16)
binary: rustc
commit-hash: 84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc
commit-date: 2023-04-16
host: x86_64-unknown-linux-gnu
release: 1.69.0
LLVM version: 15.0.7

Also tested on nightly, same result:

rustc 1.71.0-nightly (8bdcc62cb 2023-04-20)
binary: rustc
commit-hash: 8bdcc62cb0362869f0e7b43a6ae4f96b953d3cbc
commit-date: 2023-04-20
host: x86_64-unknown-linux-gnu
release: 1.71.0-nightly
LLVM version: 16.0.2

[Ezrashaw]

I suspect that this kind of metadata isn't saved to disk and therefore rustdoc has no idea about the existence of the attribute on foreign types.

[GuillaumeGomez]

That's a regression actually since it was there before #98450. Fixing it.

[nicholasbishop]

Great, thanks for the quick fix!