recuerdame
(Recuérdame: Spanish for "Remember Me")
recuerdame is a Rust procedural macro that provides compile-time function memoization. It transforms a const fn into a blazing-fast lookup table, pre-calculating all possible return values within specified input ranges.
This is ideal for computationally expensive functions with a small, discrete input domain, trading a larger binary size and longer compile times for zero-cost runtime performance.
Table of Contents
- What is
recuerdame? - Usage & Operating Modes
- How It Works
- Supported Types
- Examples
- Use Cases
- Benchmarks
- Limitations & Caveats
- License
What is recuerdame?
Imagine you have a const function that performs a complex calculation. If you call this function repeatedly with the same arguments, you're wasting cycles re-calculating the same result.
recuerdame solves this by taking your const fn and generating a static lookup table at compile time. At runtime, the new function simply performs an array lookup to get the result instantly.
The Trade-Off:
- Pro: Extremely fast (O(1)) runtime performance for in-range function calls.
- Con: Increased compile times.
- Con: Increased binary size, proportional to the size of the lookup table.
Usage & Operating Modes
-
Add
recuerdameto yourCargo.toml: -
Annotate your
const fnwith#[precalculate]and choose an operating mode. The macro gives you three ways to handle inputs that are outside the pre-calculated range.
Fallback Mode (Default)
This is the default, most flexible mode. It keeps the original function alongside the lookup table. If the inputs are in range, it uses the fast lookup table. If they are out of range, it calls the original function to compute the result on the fly. This is useful when you want fast lookups for a common "hot path" but still need to handle all other cases. This adds a small runtime cost for the bounds check.
use precalculate;
// "fallback" is optional, as it's the default behavior.
// This is equivalent to `#[precalculate(a = 0..=10, b = 0..=4, fallback)]`
pub const
// In-range uses the lookup table:
assert_eq!;
// Out-of-range calls the original function:
assert_eq!;
option Mode
This mode provides safety by wrapping the function's return type in an Option. If the inputs are within the pre-calculated range, it returns Some(value). If they are out of range, it returns None. This adds a small runtime cost for the bounds check.
use precalculate;
pub const
// Works:
assert_eq!;
// Returns None:
assert_eq!;
panic Mode
This is the fastest mode because it does not have an explicit bounds check. If an input is outside the specified range, the array access will be out of bounds, causing a panic. Use this when you can guarantee at the call site that inputs will always be in range.
use precalculate;
pub const
// Works:
assert_eq!;
// Panics: 20 is outside the specified range of 0..=10
// add_panic(20, 0);
How It Works
The #[precalculate] macro performs the following transformation at compile time:
- It creates a new, private module (e.g.,
_mod_precalc_add). - It moves your original function into this module and renames it (e.g.,
_add_original). - Inside the module, it generates a
constmulti-dimensional array that will serve as the lookup table. - It generates a
constfunction that populates this table by iterating through all possible input combinations and calling your original function. - Finally, it creates a new
pub const fnwith the original name (add). Depending on the mode, this new function either performs a bounds check before looking up the value (fallback,option) or attempts the lookup directly (panic).
This allows you to test the correctness of the macro by comparing the results against the original function, which remains accessible:
assert_eq!(add_fallback(a, b), _mod_precalc_add_fallback::_add_fallback_original(a, b));
Supported Types
Argument Types
The function arguments must be integer types (i8, u8, i16, u16, i32, u32, i64, u64, i128, u128, isize, usize) for which a range can be defined. The ranges must be inclusive, using the ..= syntax.
You can also use const values to define the ranges:
use precalculate;
const MIN_A: i16 = 0;
const MAX_A: i16 = 100;
const
Return Types (PrecalcConst trait)
The function's return type must implement the recuerdame::PrecalcConst trait. This is required to provide a default value for initializing the lookup table array before it's populated.
recuerdame provides out-of-the-box implementations for:
- All integer and float primitives (defaults to
0or0.0). - Tuples of types that implement
PrecalcConst. Option<T>whereTimplementsPrecalcConst(defaults toNone).
You can easily implement it for your own const-compatible types:
use PrecalcConst;
// Your custom struct needs to be usable in a const context.
Examples
Comparing Modes
Here is a side-by-side comparison of how each mode behaves.
use precalculate;
// 1. Fallback Mode (Default)
// fallback is implicit
const
// 2. Option Mode
const
// 3. Panic Mode
const
Using Custom Types
This example uses the custom MyColor struct defined in the Return Types section.
use ;
const
// The lookup works perfectly with custom types
assert_eq!;
Use Cases
recuerdame is most effective for:
- Digital Signal Processing (DSP): Pre-calculating sine waves, filter coefficients, or windowing functions.
- Game Development: Lookup tables for things like falloff curves, experience points, or complex physics calculations with discrete steps.
- Embedded Systems: When CPU cycles are precious and flash memory is available, replacing math-heavy functions with a lookup table can be a huge win.
- Cryptography: Pre-calculating S-boxes or other fixed tables.
Benchmarks
The core promise of recuerdame is trading compile time for a significant boost in runtime performance. The benchmarks below illustrate this by comparing a function that calculates a logistic regression value versus its pre-calculated equivalent. The benchmark measures an in-range lookup.
logistic regression (precalculated)
time: [843.09 ps 844.05 ps 845.12 ps]
logistic regression (normal)
time: [12.267 ns 12.272 ns 12.277 ns]
Analysis
- Pre-calculated (with
recuerdame): The function call takes approximately 844 picoseconds. This is effectively the cost of an array lookup. - Normal
const fn: The standard function call takes about 12.2 nanoseconds to perform the standard calculation.
In this scenario, the recuerdame-powered function is over 14 times faster than the original. This performance gap widens as the computational complexity of the target function increases.
Limitations & Caveats
-
Handling Out-of-Range Inputs: Choose your operating mode carefully. The default mode (
fallback) provides flexibility at the cost of a small runtime check. For performance-critical paths where out-of-range inputs are impossible, usepanic. If out-of-range inputs are possible and need to be handled explicitly, useoption. -
Compile Time & Binary Size: Be mindful of your input ranges. A function like
#[precalculate(a = 0..=1000, b = 0..=1000)]would try to create a table with over a million entries, drastically increasing compile time and binary size. -
const fnRequired: The macro can only be applied to functions marked asconst fn. -
Integer Arguments Required: The function arguments must be integer primitives.
License
This project is licensed under the MIT License.