Struct VectorFile 

pub struct VectorFile {
    pub algorithm: String,
    pub source: String,
    pub cases: Vec<BTreeMap<String, String>>,
    pub path: PathBuf,
}

A loaded vector file.

Fields

algorithm: String

What the file says it is for.

source: String

Where the vectors came from, for the record.

cases: Vec<BTreeMap<String, String>>

The cases, each a map of field name to raw hex string.

path: PathBuf

Where the file was found.

Implementations

impl VectorFile

pub fn load(name: &str) -> Option<VectorFile>

Load testvectors/<name>.json, or None if it is not there.

A malformed file is an error rather than a miss: someone went to the trouble of providing it, and silently ignoring it would waste their effort in the most confusing way available.

pub fn load_from(dir: &Path, name: &str) -> Option<VectorFile>

load, reading from a directory the caller names.

Exists so the tests can point at a directory of their own rather than setting IC_TEST_VECTORS – cargo runs a crate’s tests as threads in one process, so mutating the environment races every sibling that reads it.

pub fn load_or_report(name: &str) -> Option<VectorFile>

Load, or print why nothing was checked and return None.

The message is the point. A skipped vector test should be visible in the output of cargo test -- --nocapture, not inferred from its absence.