Cargo.toml

[workspace]
resolver = "3"
# Named rather than a bare `crates/*`: a scan run rooted at `crates/` drops its
# audit database in `crates/.codehelion/`, and a glob that picks that up fails
# the whole workspace with a missing manifest.
members = ["crates/codehelion-*"]

[workspace.package]
version = "0.6.0"
edition = "2024"
rust-version = "1.98"
license = "Apache-2.0"
repository = "https://github.com/libraz/codehelion"
homepage = "https://github.com/libraz/codehelion"

# Shared lint policy for every crate in the workspace (AGENTS.md §6). Each crate
# opts in with `[lints] workspace = true`.
[workspace.lints.rust]
unsafe_code = "forbid"
missing_docs = "warn"
rust_2024_compatibility = { level = "warn", priority = -1 }
unreachable_pub = "warn"
unused_qualifications = "warn"

[workspace.lints.clippy]
all = { level = "warn", priority = -1 }
pedantic = { level = "warn", priority = -1 }
nursery = { level = "warn", priority = -1 }
# Fail loudly on shortcuts that hide bugs.
unwrap_used = "warn"
expect_used = "warn"
panic = "warn"
todo = "warn"
unimplemented = "warn"
dbg_macro = "warn"

# No debug info in development builds, which is what keeps `target/` from
# growing without bound. On macOS the default keeps debug info inside the
# per-codegen-unit object files, so those objects cannot be deleted after a
# link; every rebuild names its changed units differently and leaves the
# previous ones behind, and nothing ever collects them. A test suite of this
# size reaches hundreds of thousands of stale objects in one directory within
# days, at which point every cargo invocation spends longer on filesystem calls
# than on compiling. Assertion and panic messages carry their own file and line,
# so what is given up is line numbers inside backtraces.
[profile.dev]
debug = 0

[profile.release]
strip = true
lto = true
codegen-units = 1
panic = "abort"