Struct RegistryQueryer 

pub struct RegistryQueryer<'a, T: Registry> {
    inner: Rc<RegistryQueryerAsync<'a, T>>,
    poller: LocalPollAdapter<'a, Rc<RegistryQueryerAsync<'a, T>>, (Dependency, Option<VersionOrdering>), CargoResult<Rc<Vec<Summary>>>>,
    summary_cache: HashMap<(Option<PackageId>, Summary, ResolveOpts), (Rc<(HashSet<InternedString>, Rc<Vec<(Dependency, Rc<Vec<Summary>>, Rc<BTreeSet<InternedString>>)>>)>, bool)>,
}

Wrapper around RegistryQueryerAsync that provides caching and a Poll based interface using LocalPollAdapter.

Fields

inner: Rc<RegistryQueryerAsync<'a, T>>

poller: LocalPollAdapter<'a, Rc<RegistryQueryerAsync<'a, T>>, (Dependency, Option<VersionOrdering>), CargoResult<Rc<Vec<Summary>>>>

summary_cache: HashMap<(Option<PackageId>, Summary, ResolveOpts), (Rc<(HashSet<InternedString>, Rc<Vec<(Dependency, Rc<Vec<Summary>>, Rc<BTreeSet<InternedString>>)>>)>, bool)>

a cache of Dependencys that are required for a Summary

HACK: first_version is not kept in the cache key is it is 1:1 with parent.is_none() (the first element of the cache key) as it doesn’t change through execution.

Implementations

impl<'a, T: Registry> RegistryQueryer<'a, T>

pub fn new( registry: &'a T, replacements: &'a [(PackageIdSpec, Dependency)], version_prefs: &'a VersionPreferences, ) -> Self

pub fn registry(&self) -> &T

pub fn query( &mut self, dep: &Dependency, first_version: Option<VersionOrdering>, ) -> Poll<CargoResult<Rc<Vec<Summary>>>>

pub fn wait(&mut self) -> CargoResult<bool>

pub fn used_replacement_for( &self, p: PackageId, ) -> Option<(PackageId, PackageId)>

pub fn replacement_summary(&self, p: PackageId) -> Option<Summary>

pub fn build_deps( &mut self, cx: &ResolverContext, parent: Option<PackageId>, candidate: &Summary, opts: &ResolveOpts, first_version: Option<VersionOrdering>, ) -> ActivateResult<Rc<(HashSet<InternedString>, Rc<Vec<(Dependency, Rc<Vec<Summary>>, Rc<BTreeSet<InternedString>>)>>)>>

Find out what dependencies will be added by activating candidate, with features described in opts. Then look up in the registry the candidates that will fulfil each of these dependencies, as it is the next obvious question.

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: 136 bytes