Enum Effect 

pub enum Effect {
    None,
    Quit,
    Plan(Vec<Target>),
    Delete(Vec<PathBuf>),
    Price(Vec<PathBuf>),
}

What the event loop has to do about a keystroke, once the view has done its part.

Variants

None

Nothing outside the view.

Quit

Put the terminal back.

Plan(Vec<Target>)

Resolve these into a Plan and hand it back with View::ask.

The view never plans, because planning is filesystem work — every path resolved, every check in the safety model applied — and this file has none.

Targets rather than paths, and the difference is the whole answer to “how much do I get back”: a target carries what the scan priced, and one built from a bare path carries Size::Unmeasured. Handing the planner paths made the confirmation offer to delete 196 KiB of node_modules “giving back 0 B”, with the tree saying otherwise two lines above it.

Delete(Vec<PathBuf>)

The question was answered yes. Remove exactly these.

Price(Vec<PathBuf>)

Put a size on these claims, which nobody has priced.

Filesystem work, so the view asks for it rather than doing it — the same split Plan draws. Paths and not Targets, because the whole point is that these carry no size yet: the answer comes back as the prices the walk would have sent.

Trait Implementations

impl Clone for Effect

fn clone(&self) -> Effect

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for Effect

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

Formats the value using the given formatter.

impl Eq for Effect

impl PartialEq for Effect

fn eq(&self, other: &Effect) -> bool

Equality operator ==.

fn ne(&self, other: &Rhs) -> bool

Inequality operator !=.

impl StructuralPartialEq for Effect