rustledger 0.21.0

//! Heap-profiling harness for the `load` → `process` pipeline.
//!
//! Runs the same path as `rledger check` (parse + includes + options, then
//! book + plugins + validate) over a ledger file, under dhat's heap-profiling
//! global allocator, and writes `dhat-heap.json` to the current directory on
//! exit — view it at <https://nnethercote.github.io/dh_view/>. The nightly
//! `profile.yml` workflow runs this over a generated ledger to surface
//! allocation hotspots ("where do the bytes come from") to optimize.
//!
//! ```text
//! cargo run -p rustledger --profile profiling --example profile_pipeline \
//!     --features dhat-heap -- <ledger.beancount>
//! ```
//!
//! Without the `dhat-heap` feature the example still builds and runs the
//! pipeline (no profiling), so it stays green in the default `--all-targets`
//! build.

// dhat installs a global allocator that wraps the system allocator to record
// every allocation. Gated behind the feature so the default build is untouched.
#[cfg(feature = "dhat-heap")]
#[global_allocator]
static ALLOC: dhat::Alloc = dhat::Alloc;

fn main() {
    // Profiles the whole run; on drop it writes `dhat-heap.json`.
    #[cfg(feature = "dhat-heap")]
    let _profiler = dhat::Profiler::new_heap();

    let Some(path) = std::env::args_os().nth(1) else {
        eprintln!("usage: profile_pipeline <ledger.beancount>");
        std::process::exit(2);
    };

    // Mirror `rledger check`: the one-shot `load` runs parse + includes +
    // options, then book + plugins + validate, so the profile covers the full
    // pipeline rather than just parsing.
    let options = rustledger_loader::LoadOptions {
        run_plugins: true,
        validate: true,
        ..Default::default()
    };
    match rustledger_loader::load(std::path::Path::new(&path), &options) {
        Ok(ledger) => {
            // `load` returns `Ok` even when the pipeline accumulated validation
            // errors (in `ledger.errors`, like `rledger check`). Surface the
            // count so a profile over an erroring ledger isn't silently "clean".
            eprintln!(
                "processed {} directives ({} pipeline errors)",
                ledger.directives.len(),
                ledger.errors.len()
            );
        }
        Err(e) => {
            eprintln!("load/process failed: {e}");
            std::process::exit(1);
        }
    }
}