Enum rustdoc::passes::collect_intra_doc_links::AnchorFailure [−][src]
enum AnchorFailure {
MultipleAnchors,
RustdocAnchorConflict(Res),
}
Variants
User error: [std#x#y]
is not valid
RustdocAnchorConflict(Res)
The anchor provided by the user conflicts with Rustdoc’s generated anchor.
This is an unfortunate state of affairs. Not every item that can be linked to has its own page; sometimes it is a subheading within a page, like for associated items. In those cases, rustdoc uses an anchor to link to the subheading. Since you can’t have two anchors for the same link, Rustdoc disallows having a user-specified anchor.
Most of the time this is fine, because you can just link to the page of the item if you want to provide your own anchor.
Tuple Fields of RustdocAnchorConflict
0: Res
Trait Implementations
Performs the conversion.
Auto Trait Implementations
impl RefUnwindSafe for AnchorFailure
impl Send for AnchorFailure
impl Sync for AnchorFailure
impl Unpin for AnchorFailure
impl UnwindSafe for AnchorFailure
Blanket Implementations
Mutably borrows from an owned value. Read more
Instruments this type with the provided Span
, returning an
Instrumented
wrapper. Read more
pub fn vzip(self) -> V
Attaches the provided Subscriber
to this type, returning a
WithDispatch
wrapper. Read more
Attaches the current default Subscriber
to this type, returning a
WithDispatch
wrapper. Read more
Layout
Note: Most layout information is completely unstable and may even differ between compilations. The only exception is types with certain repr(...)
attributes. Please see the Rust Reference’s “Type Layout” chapter for details on type layout guarantees.
Size: 12 bytes
Size for each variant:
MultipleAnchors
: 0 bytesRustdocAnchorConflict
: 12 bytes