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
{{ message }}
Repository navigation
cargo doc: shows different return types for re-exported methods #115760
cargo new async_doc_repro; cd async_doc_repro; cargo add smol@=1.3.0; cargo doc --open
put UdpSocket::bind into the search bar
open at the first two results
It probably also would be nice to test if this can be reproduced using a minimal setup. E.g.: are multiple crates needed? Is publicly re-exporting (with doc(inline) of a whole crate essential, the way smol does for async_net or does re-exporting a module or a function do the same, too? Etc…
Activity
steffahn commentedon Sep 11, 2023
FYI, an IMO easier way to reproduce:
cargo new async_doc_repro; cd async_doc_repro; cargo add smol@=1.3.0; cargo doc --openUdpSocket::bindinto the search barIt probably also would be nice to test if this can be reproduced using a minimal setup. E.g.: are multiple crates needed? Is publicly re-exporting (with
doc(inline)of a whole crate essential, the waysmoldoes forasync_netor does re-exporting a module or a function do the same, too? Etc…fmease commentedon Sep 12, 2023
Minimized:
Rendered as
pub async fn f() -> impl Future<Output = i32>instead ofpub async fn f() -> i32orpub fn f() -> impl Future<Output = i32>.Auto merge of rust-lang#116084 - fmease:rustdoc-fix-x-crate-async-fn,…