Autocomplete cargo doc paths/links to types in doc comment

If you write something like the following in a doc comment

/// An error returned by [`RefCell::try_borrow`](struct.RefCell.html#method.try_borrow).
#[stable(feature = "try_borrow", since = "1.13.0")]
pub struct BorrowError {
    _private: (),
}

The struct.RefCell.html#method.try_borrow your documentation site will link to the try_borrow method when you click on the RefCell::try_borrow link.

Since the naming convention for pages / links within a cargo doc generated site is consistent - could intellij-rust support autocomplete for these links?

This would make it much easier to write documentation that references other types/methods within your library.

Thanks!

[Undin]

@Kobzol PsiReferenceContributor can provide references inside element. For example, you recently implemented path completion inside string literals. And each path segment is a separate reference although it’s still a single string literal element. But from my point of view, the main problem is parsing. We need to parse markdown in doc comments to get proper PSI. And based on this PSI, we can provide features like name resolution, completion, inspections, etc. We discussed with @vlad20012 how to parse markdown not to implement parsing ourselves. One possible solution is to make the same approach that used in markdown plugin. There is platform (I mean IntelliJ platform) independent parser for markdown initially written for markdown plugin (we already use it for documentation rendering). And markdown plugin uses it to parse markdown file text to some tokens that are wrapped to PSI. We can do the same things only for doc comments. Of course, we need to solve problems that comment text contains prefixes like /// or //! but looks like it’s possible.

[Kobzol]

This would be a really useful feature indeed. @Undin we have the individual tokens that are part of a PsiComment from the doc comment lexer (RsDocElementTypes), but I don’t know what API should be used to provide name resolution for the links. I looked at PsiReferenceContributor, but it seems that it can only provide references for whole elements and not just their sub-parts.