Fast, stack-allocated linear algebra for fixed dimensions in Rust.
This crate grew from the need to support delaunay with fast, stack-allocated linear algebra primitives and algorithms
while keeping the API intentionally small and explicit.
- Introduction
- Quickstart
- Mathematical basis
- Design goals
- Anti-goals
- Use this crate when
- Scalar and bounded-value types
- Features
- API at a glance
- Documentation Map
- Benchmarks
- Examples
- Contributing
- Citation
- References
- AI Agents
- License
la-stack provides a handful of const-generic, stack-backed building blocks:
Vector<const D: usize>for fixed-lengthf64vectors backed by[f64; D]gram_matrix(&[Vector<N>; M])for allocation-freeMatrix<M>construction from pairwise vector inner products, with bit-for-bit symmetry. Gram matrices encode lengths and angles and support simplex/facet volume calculations; see Gram matrices and geometric measures. Each independent dot product is checked once; rounding has no certified error bound, and positive definiteness or affine independence must still be established by factorization or the caller. Benchmark square simplex and rectangular facet inputs through dimension 8 withcargo bench --locked --features bench --bench gram.Matrix<const D: usize>for fixed-size squaref64matrices backed by[[f64; D]; D]IntervalandIntervalMatrix<const D: usize>for outward-rounded, proof-bearing determinant filters through D=7ScalarWithErrorBoundfor proof-bearing fixed-vector dot products and affine differences over finitef64inputsRationalVector<const D: usize>andRationalMatrix<const D: usize>for exact rational inputs behind the optional"exact"featureLu<const D: usize>for LU factorization with partial pivoting (solve + det)Ldlt<const D: usize>for no-pivot factorization intended for exactly symmetric positive-definite matrices (solve + det; typed pivot diagnostics)
The minimum supported Rust version (MSRV) is 1.98.1.
Add this to your Cargo.toml:
[dependencies]
la-stack = "0.4.5"This system has solution [1, 2, 3, 4, 5] and requires partial pivoting:
use la_stack::prelude::*;
fn main() -> Result<(), LaError> {
// The zero leading entry requires LU pivoting.
let a = Matrix::<5>::try_from_rows([
[0.0, 2.0, -1.0, 1.0, 3.0],
[4.0, -1.0, 2.0, 0.0, 1.0],
[1.0, 3.0, 5.0, -2.0, 0.0],
[2.0, 0.0, -1.0, 4.0, 1.0],
[-1.0, 2.0, 0.0, 1.0, 6.0],
])?;
let b = Vector::try_new([20.0, 13.0, 14.0, 20.0, 37.0])?;
let lu = a.lu(DEFAULT_SINGULAR_TOL)?;
let x = lu.solve(b)?;
for (&actual, expected) in x.as_array().iter().zip([1.0, 2.0, 3.0, 4.0, 5.0]) {
assert!((actual - expected).abs() <= 1e-12);
}
Ok(())
}The assertion tolerance is suitable for this known example; LU does not provide a certified solution error bound.
default: no runtime dependencies; includes outward-roundedIntervalandIntervalMatrixAPIsexact: exact determinant signs, determinant values, and solves over storedf64values or caller-suppliedBigRationalinputsbench: repository-development gate used only by benchmark targets and benchmark-input tests; application crates should not enable it
la-stack operates on finite IEEE 754 binary64 values in small, fixed
dimensions. Its floating-point paths use LU with partial pivoting, LDLT without
pivoting for exactly symmetric positive-definite matrices, and closed-form
determinants through D=4. These results remain subject to conditioning and
binary64 rounding;
factorization tolerances are rejection thresholds, not accuracy guarantees. For
D≤4, direct determinants can be paired with a conservative absolute roundoff
bound when its range preconditions hold. Fixed-vector dot products and direct
affine differences can likewise return a paired estimate and certified absolute
roundoff bound without enabling arbitrary-precision dependencies.
Derived binary64 expressions can instead be assembled with Interval
subtraction, addition, multiplication, negation, and square. The resulting
IntervalMatrix<D> determinant sign is certified through D=7 when its enclosure
separates zero; the singleton [0, 0] also certifies exact zero. Every other
overlap with zero is explicitly inconclusive. This default-feature surface is
distinct from arbitrary-precision exact arithmetic.
With features = ["exact"], callers can either lift stored binary64 inputs
losslessly or supply already-exact rational inputs for exact determinant signs,
determinant values, and solves. Exactness over binary64 input starts at the
stored values and cannot recover information rounded away before construction.
See the
mathematical basis
for the algorithms, validity boundaries, and supporting references.
- ✅
const fnwhere possible (compile-time evaluation of determinants, dot products, etc.) - ✅ Const-generic storage (no dynamically sized matrix or vector representation)
- ✅
Copytypes where possible - ✅ Defined binary64 arithmetic semantics: Rust's
f64::algebraic_*operations are forbidden because their unspecified reassociation, precision, and special-value behavior is incompatible with the crate's error bounds, non-finite classification, exact fallbacks, and reproducibility contract; deliberatef64::mul_addremains allowed for its defined single-rounding semantics - ✅ Error-bounded f64 dot, affine-difference, and determinant filtering plus
optional exact signs (
dot_with_errbound,dot_difference_with_errbound,det_errbound,det_sign_exact) - ✅ Overflow- and underflow-safe Euclidean vector norms (
norm) - ✅ Outward-rounded interval expressions and division-free determinant signs through D=7, with explicit inconclusive evidence
- ✅ Exact determinant values and linear solves via optional arbitrary-precision
arithmetic (
det_exact,solve_exact, strict/rounded f64 conversions) - ✅ Explicit algorithms (LU, solve, determinant)
- ✅ Inline, stack-backed storage for core types; optional arbitrary-precision exact values allocate as required
- ✅ No runtime dependencies by default (optional features may add deps)
- ✅
unsafeforbidden
See CHANGELOG.md for release history and docs/roadmap.md for current release planning.
- Alternate scalar families:
la-stackdeliberately supports finitef64and optional exactBigRationalinput domains, notf32,f16, complex, or generic scalar APIs - Bare-metal performance: use
blasorlapackwith a native backend selected throughblas-src,lapack-src, oropenblas-src - Broad general-purpose linear algebra: use
nalgebra - Large matrices/dimensions with parallelism: use
faer
- Your matrices and vectors have small, fixed dimensions known at compile time
- Stack allocation and
Copyvalue semantics fit your data flow - You want explicit LU / LDLT / determinant APIs rather than a broad algebra toolkit
- You need exact determinants, exact determinant signs, or exact linear solves for fixed-size systems
- You need a cheap, sound interval filter for determinant expressions assembled from rounded binary64 operations
- You need a certified sign or threshold comparison for a fixed-vector dot
product or
axis · (left - right)expression - Robust predicates matter for geometry-style workloads near degeneracy
- You prefer a default build with no runtime dependencies
The public point-value scalar model deliberately has two input domains:
- finite
f64throughMatrix<D>andVector<D>for floating-point work; - arbitrary-precision
BigRationalthroughRationalMatrix<D>andRationalVector<D>behind the optional"exact"feature.
Interval is a separate bounded-value layer over finite f64 endpoints. It
encloses exact-real values during a small set of outward-rounded operations and
feeds IntervalMatrix<D> determinant proofs; it does not make Matrix generic
over alternate scalars or provide a general interval package.
This is not a generic scalar-parameterized API. Exact support intentionally
covers the robustness-sensitive operations that require it: determinant sign,
determinant value, and linear solve, followed by explicit strict or rounded
conversion when an f64 result is required. It does not promise a
BigRational counterpart for every floating-point helper or factorization.
Lower-precision f32 / f16 throughput-oriented workloads are outside the
crate's scope; they usually indicate large-matrix or accelerator-oriented use
cases better served by broader linear-algebra libraries.
det_direct_with_errbound() pairs a determinant with its certified absolute
bound, without optional dependencies. Resolve the sign when |det| > bound;
otherwise an exact fallback is needed. With exact, det_sign_exact() handles
filtering and fallback automatically.
Worked examples: the floating-point filter and exact fallback.
dot_with_errbound() and dot_difference_with_errbound() return certified
bounds for dot products and axis · (left - right) over the original stored
coordinates. Their endpoints support sign and threshold proofs; a bound that
straddles the threshold or an unavailable certificate is inconclusive.
Worked examples: dot-product signs and affine threshold tests.
det_direct() evaluates closed-form determinants in const contexts through
D=4. det() selects those formulas automatically and uses zero-tolerance LU
for larger dimensions; a failed numerical pivot remains LaError::Singular.
Compile-time example and dimension contracts.
Enable exact determinant signs, determinant values, and solves:
[dependencies]
la-stack = { version = "0.4.5", features = ["exact"] }Matrix / Vector exact methods preserve stored f64 values;
RationalMatrix / RationalVector also preserve rational expressions before
any f64 rounding. Keep exact results or explicitly choose strict versus
rounded conversion with ExactF64Conversion.
Worked examples: rational inputs, exact solves, and output conversion.
Matrix::ldlt() provides a square-root-free factorization for exactly symmetric
positive-definite matrices, supporting determinants and solves without pivoting.
Approximate symmetry is not sufficient, and floating-point success is not an
exact positive-definiteness certificate.
Worked example and typed pivot diagnostics.
Matrix::lu() uses partial pivoting for general square systems. Reuse one
Lu factorization for multiple right-hand sides or a determinant; pivot
tolerances control rejection, not solution accuracy.
Worked example: solving and reusing factors.
Interval preserves bounds while assembling differences, squares, and other
expressions. IntervalMatrix::det_sign() certifies determinant signs through
D=7: an enclosure separated from zero proves its sign, and [0, 0] proves
exact zero. Other overlaps with zero are inconclusive and may need exact fallback.
Worked example: lifted coordinates, range errors, and fallback.
Vector::norm() avoids unnecessary overflow and underflow from squaring
coordinates. norm_squared() computes the squared norm and can overflow even
when the norm is finite. Both results remain approximate, without a certified
error bound.
Worked example and range contracts.
v0.4.6 migration: Vector::norm2_sq() is renamed to Vector::norm_squared(),
the unreleased Vector::norm2() API is named Vector::norm(), and
Matrix::inf_norm() is renamed to Matrix::norm_inf(). The old method names
are removed; their numerical behavior and error contracts are unchanged by
the renames. Matrix::norm_inf() remains the maximum absolute row sum.
Start with the capability you need; the API reference lists the complete public surface, and the worked examples show how to combine operations.
| Capability | Main entry points |
|---|---|
| Vector operations and norms | Vector<D> |
| Floating-point determinants and solves | Matrix<D>, Lu<D>, Ldlt<D> |
| Gram matrix construction | gram_matrix |
| Certified dot, affine-difference, and determinant estimates | ScalarWithErrorBound, DeterminantWithErrorBound |
| Interval expressions and determinant signs | Interval, IntervalMatrix<D> |
| Exact signs, determinants, solves, and output conversion¹ | Exact arithmetic examples |
| Runtime selection of a const-generic matrix dimension | Dimension dispatch examples |
Tolerance validates numerical rejection thresholds.
LaError and its reason/location enums preserve structured
failure details; match non-exhaustive enums with a wildcard and struct-style
variants with ... See the storage, access, and error guide
for the full contracts.
¹ Requires features = ["exact"].
- API guide — worked examples, API selection, storage, and error contracts.
- Mathematical basis — algorithms, numerical guarantees, and limitations.
- Benchmarking — benchmark suites, comparison workflows, and measurement methodology.
- Performance reports — release-to-release measurement results and provenance.
- Coverage — local and CI coverage commands and report locations.
- Roadmap — release planning, future directions, and non-goals.
- Releasing — release preparation, validation, and publication.
Raw data: docs/assets/bench/vs_linalg_lu_solve_median.csv Measurement provenance: docs/assets/bench/vs_linalg_lu_solve_median.provenance.json
Representative benchmark: lu_solve factors the matrix and solves one
right-hand side. Median time is lower-is-better, and the “la-stack vs
nalgebra/faer” columns show the % time reduction relative to each baseline
(positive means the recorded la-stack median is lower). These are descriptive
point-estimate ratios, not statistical significance claims or an aggregate score
across operations.
Timings count only when the implementation preserves the documented correctness guarantees and invariants. Performance claims require comparable before-and-after evidence using the same inputs, configuration, and environment. This snapshot records the measured source state, available CPU model, operating system, Rust toolchain, dependency lock and harness digests, Criterion command, and correctness-gate result in the adjacent JSON sidecar. The publication workflow requires complete canonical-dimension coverage and regenerates the CSV, SVG, README table, and provenance together.
For the full per-kernel comparison methodology, algorithm citations, input
construction, and release-comparison workflow details, see
docs/BENCHMARKING.md.
For the current release-to-release performance snapshot, see
docs/PERFORMANCE.md.
The exact release suite includes the already-exact rational-input groups for
D=2 through D=8. Those rows report RationalMatrix::det_sign, det, and
solve alongside straightforward BigRational Gaussian determinant and solve
references. Releases produced with the rational-input harness include Criterion
point estimates and confidence intervals for these rows; comparisons against a
pre-API baseline retain them as explicit current-only measurements.
The focused interval Criterion suite covers conclusive and inconclusive
relative-coordinate lifted determinant signs at D=4 and the maximum supported
D=7 workload. Run it with just bench-interval; fixture validation stays
outside the timed closures.
The focused linear_form Criterion suite compares plain and certified dot
products and covers both well-separated and inconclusive dot/affine-difference
filters at D=4. Run it with just bench-linear-form; exact small-integer fixture
expectations are validated outside the timed closures.
| D | la-stack median (ns) | nalgebra median (ns) | faer median (ns) | reduction vs nalgebra (point est.) | reduction vs faer (point est.) |
|---|---|---|---|---|---|
| 2 | 2.044 | 4.601 | 151.939 | +55.6% | +98.7% |
| 3 | 9.989 | 23.513 | 196.357 | +57.5% | +94.9% |
| 4 | 21.865 | 54.716 | 223.910 | +60.0% | +90.2% |
| 5 | 44.510 | 71.219 | 293.420 | +37.5% | +84.8% |
| 8 | 145.405 | 188.352 | 381.872 | +22.8% | +61.9% |
| 16 | 672.491 | 585.261 | 897.236 | -14.9% | +25.0% |
| 32 | 2,777.707 | 2,501.361 | 2,952.778 | -11.0% | +5.9% |
| 64 | 17,357.785 | 13,878.401 | 12,199.761 | -25.1% | -42.3% |
The examples/ directory contains small, runnable programs:
solve_5x5— solve a 5×5 system via LU with partial pivotingdet_5x5— determinant of a 5×5 matrix via LUldlt_solve_3x3— solve a 3×3 symmetric positive definite system via LDLTconst_det_4x4— compile-time 4×4 determinant viadet_direct()exact_det_3x3— exact determinant value of a near-singular 3×3 matrix (requiresexactfeature)exact_sign_3x3— exact determinant sign of a near-singular 3×3 matrix (requiresexactfeature)exact_solve_3x3— exact solve of a near-singular 3×3 system vs f64 LU (requiresexactfeature)rational_input_5x5— exact rational solve of a 5×5 system that becomes singular as f64 (requiresexactfeature)
just examples
# or individually:
cargo run --example solve_5x5
cargo run --example det_5x5
cargo run --example ldlt_solve_3x3
cargo run --example const_det_4x4
cargo run --features exact --example exact_det_3x3
cargo run --features exact --example exact_sign_3x3
cargo run --features exact --example exact_solve_3x3
cargo run --features exact --example rational_input_5x5A short contributor workflow:
Install Rust 1.98.1 through rustup, Git,
GitHub CLI, Python 3.14,
uv 0.12.5, and jq. Then install the pinned
just release from its locked dependency graph:
cargo install --locked just --version 1.58.0
just setup # install/verify dev tools + sync Python deps + build
just check # lint/validate (non-mutating)
just fix # apply auto-fixes (mutating)
just ci # lint + tests + examples + bench compileThe repository uses cargo-nextest for runnable Rust tests, cargo-machete
for unused-dependency checks, rumdl for Markdown, dprint plus yamllint
for YAML/CFF, taplo for TOML, and typos for spelling. Python 3.14 support
tooling is locked with uv and checked by Ruff, Ty, and Semgrep. GitHub Actions
references are SHA-pinned, restricted to an explicit allowlist, and kept with
readable version comments for review.
CI runs just ci on Ubuntu, macOS, and Windows to keep platform coverage
aligned with the local comprehensive validation path.
For coverage commands and report locations, see
docs/COVERAGE.md.
For the full contributor workflow, see
CONTRIBUTING.md.
If you use this library in academic work, please cite it using CITATION.cff (or GitHub's "Cite this repository" feature). Tagged releases are archived on Zenodo under the all-versions concept DOI.
For canonical references to the algorithms used by this crate, see REFERENCES.md.
AI coding assistants should read AGENTS.md before proposing or applying changes. See CONTRIBUTING.md for the repository's AI-assisted development note.
BSD 3-Clause License. See LICENSE.
