currently, pub use statements are shown as they appear in the source, however this can be confusing if a module shares a name with a crate, see run_make_support.
under this hypothetical change, pub use libc::printf would instead appear either as pub use crate::libc::printf if libc was a module, or as pub use ::libc::printf if it was an external crate.
I think disambiguating modules to use crate:: paths could be useful. But I wouldn't change the paths starting with a crate name — the ::libc syntax is rarely used, and it's an eyesore.
my motivation is that it would allow users to tell unambiguously if a pub use refers to a crate, or if it refers to a module and the documentation page just hasn't been regenerated.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.