Enum rustdoc::passes::collect_intra_doc_links::ResolutionFailure

enum ResolutionFailure<'a> {
    WrongNamespace(Res, Namespace),
    CannotHaveAssociatedItems(Res, Namespace),
    NotInScope {
        module_id: DefId,
        name: Cow<'a, str>,
    },
    NoPrimitiveImpl(Res, String),
    NoPrimitiveAssocItem {
        res: Res,
        prim_name: &'a str,
        assoc_item: Symbol,
    },
    NoAssocItem(Res, Symbol),
    NoParentItem,
    NotAVariant(Res, Symbol),
    Dummy,
}

Variants

WrongNamespace(Res, Namespace)

This resolved, but with the wrong namespace. Namespace is the expected namespace (as opposed to the actual).

CannotHaveAssociatedItems(Res, Namespace)

This has a partial resolution, but is not in the TypeNS and so cannot have associated items or fields.

NotInScope

name is the base name of the path (not necessarily the whole link)

Fields of NotInScope

module_id: DefIdname: Cow<'a, str>

NoPrimitiveImpl(Res, String)

this is a primitive type without an impls (no associated methods) when will this actually happen? the Res is the primitive it resolved to

NoPrimitiveAssocItem

[u8::not_found] the Res is the primitive it resolved to

Fields of NoPrimitiveAssocItem

res: Resprim_name: &'a strassoc_item: Symbol

NoAssocItem(Res, Symbol)

[S::not_found] the String is the associated item that wasn't found

NoParentItem

should not ever happen

NotAVariant(Res, Symbol)

this could be an enum variant, but the last path fragment wasn't resolved. the String is the variant that didn't exist

Dummy

used to communicate that this should be ignored, but shouldn't be reported to the user

Implementations

impl<'a> ResolutionFailure<'a>

fn res(&self) -> Option<Res>

fn full_res(&self) -> Option<Res>

Trait Implementations

impl<'a> Debug for ResolutionFailure<'a>

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl<'a> From<ResolutionFailure<'a>> for ErrorKind<'a>

fn from(err: ResolutionFailure<'a>) -> Self

Performs the conversion.