You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As i understand it, #[doc(inline)] properly applies to local glob re-exports, but apparently not for cross-crate ones. This is not being handled correctly.
The text was updated successfully, but these errors were encountered:
When cleaning an import statement, rustdoc will only load an item if the import is not a glob import. If it is a glob import, it instead registers the underlying path (which i believe is the module/enum path) and leaves the import statement alone. It would instead be prudent to check the import statement for #[doc(inline)] (done already and saved in denied), check whether the glob import is based in a module, scan that module for its items, then import all those items, just like what it does for single-item imports.
rustdoc: process cross-crate glob re-exports
Turns out, we were deliberately ignoring glob re-exports when they were occurring across crates, even though we were fully processing them for local re-exports. This will at least bring the two into parity.
Fixes#51252
cf. This is the
std::alloc
docs page:...but this is how those items are declared:
As i understand it,
#[doc(inline)]
properly applies to local glob re-exports, but apparently not for cross-crate ones. This is not being handled correctly.The text was updated successfully, but these errors were encountered: