1946-intra-rustdoc-links issue

[olegnn]

Problem

Links created according to 1946-intra-rustdoc-links either don't work as expected or work with warning: `[...]` cannot be resolved, ignoring it....

Steps

1. Go to https://rust-lang-nursery.github.io/futures-api-docs/0.3.0-alpha.18/futures/channel/mpsc/struct.TryRecvError.html.
2. Click on try_next link.
   It won't work correctly, but if we
3. git clone https://github.com/rust-lang-nursery/futures-rs
4. cd futures-rs
5. Change line
   from
   [`try_next`](Receiver::try_next)
   to
   [`try_next`](mpsc::Receiver::try_next())
   or to
   [`try_next`](futures_channel::mpsc::Receiver::try_next())
6. After cargo +nightly doc
   we will get
   warning: `[mpsc::Receiver::try_next]` cannot be resolved, ignoring it...
   or
   warning: `[futures_channel::mpsc::Receiver::try_next]` cannot be resolved, ignoring it...
   respectively.

Meanwhile link will magically work.

Possible Solution(s)

It would be nice to remove incorrect warnings and make doc example work [or at least add warning for that case]. Thanks.

Notes

Output of cargo version:

cargo 1.39.0-nightly (22f7dd049 2019-08-27)

[ehuss]

Transferred to rust-lang/rust since this is a rustdoc issue.

[tesuji]

Link to the tracking issue of intra doc link: #43466

[jyn514]

Possible duplicate of #73699 (I know this issue came first but the other has a MCVE).

[jyn514]

Closing as duplicate of #73699: futures_rs is trying to link to the upstream crate futures_channel.

[Nemo157]

This isn't related to #73699/#74481, it's just normal cross-crate inlining intradoc issues.

On futures-channel::mpsc::TryRecvError the link is correctly resolved, on futures::mpsc::TryRecvError it is not. I tried building with the latest nightly (rustdoc 1.46.0-nightly (346aec9b0 2020-07-11)) and it still doesn't work, @jyn514 are there still known cross-crate inlining issues, or should they all be fixed now? (:facepalm: that's not latest nightly, I forgot about the fallback for missing components and I have an entire screen-full of components installed so the messages disappear, I'll retest).

[Nemo157]

Testing with actual latest nightly works 🎉 so this will be fixed for the next version published.