An R&D project that explores adding evaluation as a first-class-citizen to the typenum crate.
Typenum treats constant values and evaluation the way it ought to be treated:
- Unconcerned with machine representation (u64, usize, i32, etc)
- Specifications in the type-system (
fn foo<F: IsGreater<U8>()) - Compile-time and Execution-time code is explicitly separated
The shortfall of typenum, is that evaluation is not provided. The operation ((x + 4) * Y) / Z must be expressed like so:
This process of saying "the type-values passed in must be able to perform this arithmetic" is now done internally through the *Expr traits (Num/Bool/Ord/other expression traits):
Limitations
Currently negative numbers are not yet implemented.
The strategy for implementing division requires type-resolution capabilities made available in nightly-2024-10-17. This should be improved in the near future.
The following operations are implemented: if, +, -, *, /, <<, >>, <, >, <=, >=, ==, cmp
The error output is in a messy binary form. The plan is to make this more readable.
Future work
In very approximate order of priority:
- Runtime number expression
- Robust property/fuzz testing
- negative numbers
- Move from binary to decimal representation
- More readable errors
- implementation of an
opmacro (replaceIF<LT<X, Y>, Add<Div<X, U2>, Y>, Z>withop!(if X < Y {(X + 2)/ Y} else {Z})) - Explore use of
struct U238...instead oftype U238 = ... - Usable in place of a
usizetype in declaring array lengths. matchexpression impl- closure expression impl
- any-type expression (i.e. Bool/Num/Ord expressions all impl the generic expression)
- Upstreaming into a nursary/nightly feature.