buildline 0.4.2

One timeline for your whole build, no matter how many build systems it's made of.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33

//! Per-tool adapters: native profiling format → normalized [`Span`]s.
//!
//! Each adapter is a pure function (no I/O, no clocks) pinned by a golden-file
//! test. Adding support for a new build system means adding one file here and
//! one fixture pair — nothing else moves. See `CONTRIBUTING.md` for the exact
//! shape.
//!
//! Currently supported: [`ninja`], [`cargo`], [`webpack`], [`generic`]
//! (Chrome Trace Event Format pass-through).
use crate::span::Span;

pub mod cargo;
pub mod generic;
pub mod ninja;
pub mod webpack;

/// Tool names the `buildline` wrapper knows how to capture. The single source
/// of truth for "what's supported today", surfaced in the wrapper's error
/// message so it can never drift out of sync with the actual match arms.
pub const SUPPORTED_TOOLS: &[&str] = &["ninja", "cargo", "webpack"];

/// Parses one build tool's native profiling artifact into relative spans.
///
/// Each adapter is a pure function of its input bytes, no clocks, no I/O, so
/// its behavior is pinned by a golden-file test (fixture in, expected JSON out).
/// A new build system = a new file here + a fixture pair. Nothing else moves.
pub trait Adapter {
    /// Short id, e.g. `ninja`. Also the default track name.
    fn name(&self) -> &'static str;

    /// Parse native bytes into spans whose `start_us` is relative to the tool's T0.
    fn parse(&self, input: &[u8]) -> anyhow::Result<Vec<Span>>;
}