Module items not in scoped for module `//!` comment when module also has `///` comment

[xmppftw]

Not very clear how //! in top of module or /// before 'mod' declaration works and what difference. I found one big difference when doing /// then in rest of //! at top of module, module items are not in the scoped.

I understand it's normal module importer doesnt ahve module items in scoped by default. But its not normal that module itself doesnt have items in the scoped.

Smallest reproduction case: https://github.com/xmppftw/rustrepro/tree/issue-134904

• maybe it's a bug?
• maybe it's bad to use /// and //! but i dont see this in rustdoc book or somewhere else

[aDotInTheVoid]

Minimal:

/// Outer doc-comment.
pub mod demo {
    //!
    //! Inner doc-comment with link: [`DemoStruct`]

    pub struct DemoStruct;
}

Which produces the following warning:

warning: unresolved link to `DemoStruct`
 --> ./src/lib.rs:4:40
  |
4 |     //! Inner doc-comment with link: [`DemoStruct`]
  |                                        ^^^^^^^^^^ no item named `DemoStruct` in scope
  |
  = help: to escape `[` and `]` characters, add '\' before them like `\[` or `\]`
  = note: `#[warn(rustdoc::broken_intra_doc_links)]` on by default

warning: 1 warning emitted

and doesn't resolve the link:

---

Whereas if you remove the outer doc-comment, it works as expected:

---

I think this is happening because we merge the outer and inner doc-comment before resolving intra-doc-links (but I've not checked).

[lolbinarycat]

possible duplicate of #119965?