tpt-data-parsers

A Rust workspace of ultra-fast, zero-allocation parsers for formats the broader ecosystem ignores.

Each crate is published independently to crates.io and is designed to be dropped into a pipeline, a log shipper, or a constrained (no_std) target without pulling in a heavy dependency tree.

Crates

Crate	Description	crates.io	docs.rs
tpt-jsonl-stream	Streaming, zero-allocation JSON Lines parser
tpt-geo-geojson	Strict, validating GeoJSON parser with line-numbered errors
tpt-logfmt-parse	Zero-copy logfmt (key=value) parser
tpt-cron-parse	Cron expression parser with human-readable output
tpt-mime-pure	Pure Rust MIME type detection via magic bytes (no_std)

Which crate do I need?

• I have newline-delimited JSON (.jsonl / NDJSON) and want to iterate records without loading everything into memory → tpt-jsonl-stream.
• I have GeoJSON and need strict validation with precise error locations → tpt-geo-geojson.
• I'm parsing structured logs of the form key=value key="quoted value" → tpt-logfmt-parse.
• I have a cron schedule string and want a human-readable description or precise parse errors → tpt-cron-parse.
• I need to identify a file's type from its bytes or extension (no file binary) → tpt-mime-pure.

If you only have a filename/path rather than raw bytes, tpt-mime-pure's detect_by_extension is the right tool. If you have raw bytes, use detect.

Design principles

• Zero / low allocation where it matters — most crates parse without allocating in the hot path (tpt-logfmt-parse, tpt-jsonl-stream).
• Minimal dependencies — tpt-cron-parse, tpt-mime-pure, and tpt-logfmt-parse have no runtime dependencies; tpt-jsonl-stream only depends on serde_json (with an optional simd fast path).
• Precise errors — parsers report byte positions, line numbers, or structure paths instead of opaque failures.
• no_std capable — tpt-mime-pure works without the standard library (its std feature is default; disable it via default-features = false).

Workspace & contributing

• This is a Cargo workspace (resolver = "2", edition 2021, MSRV 1.70). Shared metadata lives in the root Cargo.toml via workspace = true; member crates must not hardcode it.
• See AGENTS.md for the exact verify/test/publish commands (cargo fmt / cargo clippy -D warnings / cargo test), and per-crate publishing on v*.*.* tags.
• CONTRIBUTING.md documents how to set up, the CI sequence to run locally, and the project conventions.
• Each crate ships a runnable example under its examples/ directory (run with cargo run -p <crate> --example <name>).

License

Licensed under either of:

• Apache License, Version 2.0 (LICENSE-APACHE)
• MIT license (LICENSE-MIT)

at your option.