Struct WalkOutcome 

pub struct WalkOutcome {
    pub manifests: Vec<DiscoveredManifest>,
    pub walk_errors: Vec<String>,
    pub truncated: bool,
    pub unrecognized_explicit_paths: Vec<PathBuf>,
    pub ignored_manifests: Vec<PathBuf>,
}

The result of walking one or more roots.

Fields

manifests: Vec<DiscoveredManifest>

Every manifest discovered and routed to an ecosystem.

walk_errors: Vec<String>

Paths that ignore could not read (permission error, broken symlink, …) — reported as warnings, never fatal (FR-002’s “no ecosystem recognizes / cannot be read” edge case).

truncated: bool

Whether MAX_WALKED_FILES was reached before the walk finished.

unrecognized_explicit_paths: Vec<PathBuf>

A root that was itself a single file (not a directory) but that no ecosystem’s manifest_filenames/manifest_patterns/manifest_extensions/ manifest_directory_patterns claimed (M4, spec 062 review) — spec §6 requires a warning line for exactly this case: an explicitly-given path, unlike an unmatched file encountered while walking a directory (the overwhelming majority of files in any real tree, never worth a warning each).

ignored_manifests: Vec<PathBuf>

Manifest-shaped files excluded from the scan without the caller asking for that exclusion — either an ignore rule while respect_gitignore was enabled (issue #1109), or a PRUNED_DIRECTORIES match in any mode (reviewer follow-up: an unusual monorepo layout can have a real subproject’s manifest sitting directly inside a directory named vendor/build/dist/…). Unlike unrecognized_explicit_paths, this is a warning about data loss (a real manifest silently skipped), not a benign non-match.

Trait Implementations

impl Default for WalkOutcome

fn default() -> WalkOutcome

Returns the “default value” for a type.