Struct FileOutcome 

pub struct FileOutcome {
    pub file: PathBuf,
    pub applied: Vec<Applied>,
    pub skipped: Vec<Skipped>,
    pub deferred: usize,
    pub reverted: Option<String>,
    pub oscillation: Option<String>,
    pub contents: Option<String>,
    pub suggested: Option<String>,
    pub check: CheckInfo,
}

Everything one file’s run of fix_file did, and everything it declined to do.

A run that changed nothing still fills this in: the skips are the answer to “why did htl fix do nothing”, and without them a filtered run and a clean file look alike.

Fields

file: PathBuf

The file this is about.

applied: Vec<Applied>

Fixes that landed, in the order the passes applied them.

skipped: Vec<Skipped>

Fixes that did not, each with its reason.

deferred: usize

Edits deferred because they overlapped an applied one and the pass cap hit.

reverted: Option<String>

The file was put back as it was because a fix introduced an error.

oscillation: Option<String>

Two passes produced the same edit set: the rules named undo each other.

contents: Option<String>

The new contents (dry run: what would be written); None when unchanged.

suggested: Option<String>

The file as the suggest fixes would additionally leave it, over whatever was applied. Never written: a suggestion is shown and the value in it is the author’s to choose (htl fix --diff is where it is shown). None when there are none.

check: CheckInfo

Diagnostics after the last pass (what htl check would now say).

Trait Implementations

impl Debug for FileOutcome

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

Formats the value using the given formatter.

impl Default for FileOutcome

fn default() -> FileOutcome

Returns the “default value” for a type.