Module context 

Re-exports

use super::RequestedFeatures; 🔒

use super::dep_cache::RegistryQueryer; 🔒

use super::errors::ActivateResult; 🔒

use super::types::ActivationsKey; 🔒

use super::types::ConflictMap; 🔒

use super::types::ConflictReason; 🔒

use super::types::FeaturesSet; 🔒

use super::types::ResolveOpts; 🔒

use crate::util::Graph; 🔒

use crate::util::interning::INTERNED_DEFAULT; 🔒

use crate::util::interning::InternedString; 🔒

use crate::workspace::Dependency; 🔒

use crate::workspace::PackageId; 🔒

use crate::workspace::Registry; 🔒

use crate::workspace::Summary; 🔒

use anyhow::format_err; 🔒

use cargo_util::collections::HashMap; 🔒

use cargo_util::collections::HashSet; 🔒

use std::collections::BTreeSet; 🔒

use tracing::debug; 🔒

Structs

ResolverContext

Type Aliases

Activations

Find the activated version of a crate based on the name, source, and semver compatibility. By storing this in a hash map we ensure that there is only one semver compatible version of each crate. This all so stores the ContextAge.

ContextAge

When backtracking it can be useful to know how far back to go. The ContextAge of a Context is a monotonically increasing counter of the number of decisions made to get to this state. Several structures store the ContextAge when it was added, to be used in find_candidate for backtracking.