Struct FragmentCorpus 

pub struct FragmentCorpus { /* private fields */ }

Every fragment file’s text, scanned at most once however many times the packs around it are loaded (ADR-0018).

One proef test loads packs up to four times — the suite, then [run] setup and [run] teardown, each validated and then run — against different feature paths but always the same corpus. Rescanning per load measured ~75% of a run’s total work on a 200-file corpus, and it grows with the corpus, which is the direction adoption goes.

The memo lives here rather than in the caller because the scan must stay lazy: load_collecting runs it only when some pack actually has a ref:, which is what makes CONFIG.md’s “pointing at a corpus you did not write costs nothing” true of the scan. A caller that scanned eagerly in order to share the result would buy speed by breaking that promise. Nothing here reads a file — the texts arrive already read, so core stays sans-IO.

Implementations

impl FragmentCorpus

pub fn new(sources: Vec<PackSource>, kinds: &[StepKindSpec]) -> Self

A corpus over already-read file texts.

pub fn with_read_errors(self, errors: Vec<Diag>) -> Self

Record files the caller could not read. They are reported like any other per-file corpus problem — never sinking their siblings, and never at all unless something ref:s the corpus.

pub fn empty() -> Self

The empty corpus — no [run] fragments configured, so no ref: can resolve and nothing is ever scanned.

pub fn fragments(&self) -> &BTreeMap<String, Fragment>

Every annotated fragment in the corpus, keyed by name. Scans on first use, like every other reader.

Public because the scan is otherwise gated: load parses the corpus only when some pack actually names a fragment, so PackSet::fragments is empty for a suite that references none — which is exactly the suite a listing has the most to say about.

pub fn unannotated(&self) -> &BTreeMap<String, Vec<usize>>

Per file, the 1-based lines of entries carrying no # @proef annotation — the one class of corpus content nothing else can report, since an unannotated entry has no name to be listed by.

pub fn diagnostics(&self) -> &[Diag]

Whatever was wrong with the corpus: unreadable files first, then scan failures. Already shaped as diagnostics.

Trait Implementations

impl Debug for FragmentCorpus

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

Formats the value using the given formatter.