Skip to main content

Module errors

Module errors 

Source

Re-exportsยง

use std::fmt; ๐Ÿ”’
use std::fmt::Write as _; ๐Ÿ”’
use std::path::Path; ๐Ÿ”’
use std::path::PathBuf; ๐Ÿ”’
use crate::sources::IndexSummary; ๐Ÿ”’
use crate::sources::path::RecursivePathSource; ๐Ÿ”’
use crate::sources::source::QueryKind; ๐Ÿ”’
use crate::util::edit_distance::closest; ๐Ÿ”’
use crate::util::edit_distance::edit_distance; ๐Ÿ”’
use crate::util::errors::CargoResult; ๐Ÿ”’
use crate::util::GlobalContext; ๐Ÿ”’
use crate::util::OptVersionReq; ๐Ÿ”’
use crate::util::VersionExt; ๐Ÿ”’
use crate::workspace::Dependency; ๐Ÿ”’
use crate::workspace::PackageId; ๐Ÿ”’
use crate::workspace::Registry; ๐Ÿ”’
use crate::workspace::Summary; ๐Ÿ”’
use anyhow::Error; ๐Ÿ”’
use super::VersionPreferences; ๐Ÿ”’
use super::context::ResolverContext; ๐Ÿ”’
use super::types::ConflictMap; ๐Ÿ”’
use super::types::ConflictReason; ๐Ÿ”’

Structsยง

ResolveError
Error during resolution providing a path of PackageIds.

Enumsยง

ActivateError

Functionsยง

activation_error ๐Ÿ”’
alt_names ๐Ÿ”’
Maybe the user mistyped the name? Like dep-thing when Dep_Thing was meant. So we try asking the registry for a fuzzy search for suggestions.
alt_paths ๐Ÿ”’
For path dependencies, scan the dependency directory for any packages that exist in subdirectories. This helps when the user points to a directory without a Cargo.toml or with the wrong package name.
alt_versions ๐Ÿ”’
describe_path ๐Ÿ”’
Returns String representation of dependency chain for a particular pkgid.
describe_path_in_context ๐Ÿ”’
Returns String representation of dependency chain for a particular pkgid within given context.
rejected_versions ๐Ÿ”’
Maybe something is wrong with the available versions

Type Aliasesยง

ActivateResult