relmath
relmath is the library crate inside the relmath-rs repository.
It provides exact finite relations with deterministic BTreeSet-backed
iteration order.
Current Surface
The current public API covers:
UnaryRelation<T>for finite unary relations (sets)BinaryRelation<A, B>for finite binary relationsGroupedRelation<T>for deterministic exact grouped n-ary outputNaryRelation<T>for deterministic schema-aware exact n-ary relations- schema validation with explicit n-ary relation errors
- named-column inspection with zero-based
column_index - std-only named-row onboarding and export with
BTreeMap - union, intersection, and difference
- domain, range, converse, and composition
- domain/range restriction plus image/preimage with unary relations
- identity on a carrier
- transitive and reflexive-transitive closure on homogeneous relations
- relation property checks for reflexivity, irreflexivity, symmetry, antisymmetry, transitivity, equivalence, and partial order
- n-ary schema inspection, row insertion, deterministic iteration, selection, projection, rename, natural join, and schema-compatible set algebra
Composition uses relational order:
r.compose(&s)meansr ; s- the result contains
(a, c)when somebsatisfies(a, b) in rand(b, c) in s
Current Limits
This crate currently implements the exact G1 core plus the first narrow G2 foundation:
- natural join plus exact keyed grouping with row counts have landed so far; broader join families, richer aggregation, and division are still later work
- no typed row derives or schema macros yet
- no weighted or temporal relations
- no solver-backed or symbolic evaluation
The repository ships focused examples under examples/:
familyfor ancestry and reachabilityaccess_controlfor role-permission propagationworkflowfor state reachabilitycurriculumfor schema-aware n-ary filtering and projection
N-ary Row Algebra Notes
selectkeeps the existing schema and preserves deterministic order among surviving rowsprojectfollows the requested column order exactlyprojectcurrently rejects empty projections and duplicate projected columnsrenameis a no-op when the source and target names are the sameunion,intersection, anddifferencerequire exact schema equality, including column order
N-ary Interchange Notes
- the current G2 interchange boundary is std-only and dependency-free
from_named_rowsloadsBTreeMaprecords into an explicit schemato_named_rowsexports name-addressableBTreeMaprecords in deterministic row order- missing and unexpected columns are rejected explicitly
- serde, JSON, and CSV / TSV onboarding remain later feature-gated work
N-ary Join Notes
natural_joinmatches rows when every shared column has equal values- when two schemas are disjoint,
natural_joinbehaves as a cartesian product - the output schema keeps the entire left schema, then appends right-only columns in their original order
- output row order stays deterministic because rows are materialized into a
BTreeSet - if no rows match, the result is empty but still carries the joined schema
N-ary Grouping Notes
group_byuses explicit key columns in the requested ordergroup(key)returns the member relation for one exact grouping key- empty grouping keys are currently rejected by the exact core
- each member group keeps the original relation schema in this first slice
- group iteration order is deterministic by key
countsis the first exact aggregate and returns the number of stored rows in each group after relation deduplication
Example
use BTreeMap;
use NaryRelation;
let completed = from_named_rows?;
let rooms = from_named_rows?;
let scheduled = completed.natural_join;
let by_room = scheduled.group_by?;
assert_eq!;
assert_eq!;
assert_eq!;
# Ok::
Status
This crate now contains the published G1 unary/binary core plus the first schema-aware n-ary building block for G2, including stricter schema validation for blank column names, a std-only named-row interchange boundary, an exact natural join primitive, and exact keyed grouping with row counts.