rust-tool-base

The Rust counterpart to go-tool-base, and deliberately not a straight port. Rather than copy the Go version wholesale, it reimagines the same idea through Rust idioms and off-the-shelf crates, while keeping a common signature and feature set so the two feel familiar if you switch between them. The same streamlined developer experience, done the Rust way.

Storage answers where a secret lives, not what happens to it in memory. Wrapping secrets so they redact in Debug and zero on drop.

O_APPEND only guarantees non-interleaved writes below PIPE_BUF, which is 4096 bytes on Linux. A fat JSONL event above that splices two lines.

A lowest-common-denominator AI interface throws away what each provider is good at. When to route through an abstraction and when to drop below it.

Go funnels errors through a handler. In Rust, diagnostics carry their own code and help and propagate on their own, so the funnel disappears.

Runtime feature flags decide which commands are reachable on a given run. Cargo features decide what is compiled in at all. Do not confuse them.

forbid(unsafe_code) is absolute, which is a problem when a dependency emits a link_section the lint counts as unsafe. Where the line ends up.

Why every shipping crate uses forbid(unsafe_code) rather than deny, which any module inside it can quietly override from the inside.

Hot-reloading configuration: watch the file, re-read it, swap it in atomically and notify observers, without restarting a long-running service.

A vulnerability scanner is a one-day yes or no. Running cargo-deny as a standing policy gate instead, with waivers that expire on a date.

Go functional options enforce required fields at runtime, if at all. A Rust typestate builder refuses to compile when you forget one.