Change:
<ins> error: unresolved link to `Foo::X` --> $DIR/value-ctor.rs:5:6 | LL | /// [value@Foo::X] |      ^^^^^^^^^^^^ this link resolves to the variant `X`, which is not in the value namespace | note: the lint level is defined here --> $DIR/value-ctor.rs:2:9 | LL | #![deny(rustdoc::broken_intra_doc_links)] |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: to link to the variant, prefix with `variant@` | LL | /// [variant@Foo::X] |      ~~~~~~~~ error: unresolved link to `MyStruct` --> $DIR/value-ctor.rs:10:11 | LL | /// [tst][value@MyStruct] |           ^^^^^^^^^^^^^^ this link resolves to the struct `MyStruct`, which is not in the value namespace | help: to link to the struct, prefix with `struct@` | LL | /// [tst][struct@MyStruct] |           ~~~~~~~ error: unresolved link to `Internals` --> $DIR/value-ctor.rs:20:15 | LL | /// while [b][value@Internals] fails. |               ^^^^^^^^^^^^^^^ this link resolves to the struct `Internals`, which is not in the value namespace | help: to link to the struct, prefix with `struct@` | LL | /// while [b][struct@Internals] fails. |               ~~~~~~~ error: incompatible link kind for `Internals` --> $DIR/value-ctor.rs:22:15 | LL | /// while [d][variant@Internals] fails. |               ^^^^^^^^^^^^^^^^^ this link resolved to a struct, which is not a variant | help: to link to the struct, prefix with `struct@` | LL | /// while [d][struct@Internals] fails. |               ~~~~~~~ error: unresolved link to `Internals2` --> $DIR/value-ctor.rs:34:15 | LL | /// while [b][value@Internals2] fails. |               ^^^^^^^^^^^^^^^^ this link resolves to the enum `Internals2`, which is not in the value namespace | help: to link to the enum, prefix with `enum@` | LL | /// while [b][enum@Internals2] fails. |               ~~~~~ error: aborting due to 5 previous errors </ins>

Discussion:
I'm probably planning on working on this, I found it while I was working on . The issue is that rustdoc looks up in the value namespace, which returns a Ctor, not a Variant. Turns out giving doc comments unimpeded access to the rustc resolver might not be a perfect idea This seems slightly (but not very) tricky to fix, mainly an ironing out of semantics - do we pretend that in the value namespace doesn't exist? Or do we let you reference it, but taking care not to say that there's a conflict between (the constructor) and (the variant) and that you have to disambiguate it? <!-- If you're using the stable version of the compiler, you should also check if the bug also exists in the beta or nightly versions. --(current master): <!-- Include a backtrace in the code block by setting in your environment. E.g. . --<details<summary<strongBacktrace</strong</summary<p</p</details
i'm not sure why we would want this - you can't document the constructor separately from the variant, so i would expect rustdoc to hide it from intra-doc links
(or alternatively we could make an alias for )
First of all, I can reproduce this problem with a unit-like struct. Second of all, This is an observable fact. To see it, use glob exports. Most crates probably won't do this... but most crates probably won't need disambiguators at all. These things are in the value namespace, and that's a fact that can be observed in the surface language, so we probably shouldn't pretend otherwise.