Struct Config 

pub struct Config {
    pub bench: BTreeMap<String, Bench>,
    pub env: Option<EnvSection>,
    pub gate: Option<GateSection>,
    pub report: Option<ReportSection>,
}

Fields

bench: BTreeMap<String, Bench>

Benchmarks by name. A BTreeMap so runs are ordered and reproducible rather than following the file’s incidental key order.

env: Option<EnvSection>

Project-level environment settings. See settings.toml for what these mean; this type only says where they can be written.

gate: Option<GateSection>

Regression-gate settings.

report: Option<ReportSection>

Report-rendering settings.

Implementations

impl Config

pub fn parse(text: &str) -> Result<Self>

pub fn find_settings(start: &Path) -> Result<SettingsSections>

Read the setting tables, without validating benchmarks.

Settings and benchmarks live in the same file but are needed at different times. Resolving settings through Config::parse would make a broken [bench.x] abort tak run -- somecmd, which does not read benchmarks at all, and tak settings, which reads none of them either.

Unknown keys are ignored, so [bench] is not even looked at here. A TOML syntax error still fails: the file may carry [env] settings that change what gets scrubbed from a subject’s environment, and quietly falling back to defaults would apply a weaker filter than the project asked for without saying so.

pub fn find(start: &Path) -> Result<Option<(PathBuf, Self)>>

Find and load tak.toml, searching upward from start.

Walking up means tak run behaves the same from a subdirectory as from the repository root, which is where people actually are.

Trait Implementations

impl Debug for Config

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

Formats the value using the given formatter.

impl<'de> Deserialize<'de> for Config

fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error>

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.