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
// foo/src/lib.rs/// Documentation for this reexport.#[doc(inline)]pubuse bar::Bar;
When putting the cursor over a reexported type, VSCode does not show the docs from the reexport.
In the example above, when using the reexported Bar type from foo, VSCode does not display Documentation for this reexport. as part of the Bar documentation.
Instead it would only show the documentation set for Bar at the bar crate, if any.
The text was updated successfully, but these errors were encountered:
// bar/src/lib.rspubstructBar;// foo/src/lib.rs/// Documentation for this reexport.#[doc(inline)]pubuse bar::Bar;// baz/src/lib.rsuse foo::Bar;fnfoo() -> Bar{ ...}
When hovering over the return type of foo(), we have no way to tell the reexport it came from. All we know is the use in baz and the original definition. And I think it'll be quite confusing if we would show it only when hovering over the direct reexport.
rust-analyzer version: 0.3.2345-standalone (b0632f7 2025-03-16)
rustc version: rustc 1.86.0-nightly (ae5de6c75 2025-01-29)
editor or extension: VSCode
code snippet to reproduce:
When putting the cursor over a reexported type, VSCode does not show the docs from the reexport.
In the example above, when using the reexported
Bar
type fromfoo
, VSCode does not displayDocumentation for this reexport.
as part of theBar
documentation.Instead it would only show the documentation set for
Bar
at thebar
crate, if any.The text was updated successfully, but these errors were encountered: