pub fn refuse_baseline_kind_overwrite(
save_path: &Path,
saving: BaselineKind,
) -> Option<String>Expand description
Why a --save-baseline must not overwrite the file at save_path, or None
when the save may proceed.
A save serializes a fresh struct over the whole file, so one command’s save
aimed at another command’s baseline destroys it with nothing left to recover
from. Read from the destination’s own kind: a file saved before that member
existed carries nothing to identify it and is still overwritten silently, and
an unreadable or absent destination is not a guard condition, exactly as the
health identity-overwrite guard treats one.