5 releases (3 breaking)

Uses new Rust 2024

0.4.0 Jul 20, 2025
0.3.1 Jul 18, 2025
0.2.1 Jul 17, 2025
0.1.0 Jul 17, 2025

#1036 in Rust patterns

MIT license

17KB
78 lines

recuerdame

crates.io docs.rs

(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?

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

  1. Add recuerdame to your Cargo.toml:

    cargo add recuerdame
    
  2. Annotate your const fn with #[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 recuerdame::precalculate;

// "fallback" is optional, as it's the default behavior.
// This is equivalent to `#[precalculate(a = 0..=10, b = 0..=4, fallback)]`
#[precalculate(a = 0..=10, b = 0..=4)]
pub const fn add_fallback(a: i32, b: i32) -> i32 {
    a + b
}

// In-range uses the lookup table:
assert_eq!(add_fallback(5, 2), 7);
// Out-of-range calls the original function:
assert_eq!(add_fallback(20, 0), 20);

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 recuerdame::precalculate;

#[precalculate(a = 0..=10, b = 0..=4, option)]
pub const fn add_option(a: i32, b: i32) -> i32 {
    a + b
}

// Works:
assert_eq!(add_option(5, 2), Some(7));
// Returns None:
assert_eq!(add_option(20, 0), None);

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 recuerdame::precalculate;

#[precalculate(a = 0..=10, b = 0..=4, panic)]
pub const fn add_panic(a: i32, b: i32) -> i32 {
    a + b
}

// Works:
assert_eq!(add_panic(5, 2), 7);
// 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:

  1. It creates a new, private module (e.g., _mod_precalc_add).
  2. It moves your original function into this module and renames it (e.g., _add_original).
  3. Inside the module, it generates a const multi-dimensional array that will serve as the lookup table.
  4. It generates a const function that populates this table by iterating through all possible input combinations and calling your original function.
  5. Finally, it creates a new pub const fn with 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 recuerdame::precalculate;

const MIN_A: i16 = 0;
const MAX_A: i16 = 100;

#[precalculate(a = MIN_A..=MAX_A)]
const fn my_func(a: i16) -> i32 {
    (a * a) as i32
}

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 0 or 0.0).
  • Tuples of types that implement PrecalcConst.
  • Option<T> where T implements PrecalcConst (defaults to None).

You can easily implement it for your own const-compatible types:

use recuerdame::PrecalcConst;

// Your custom struct needs to be usable in a const context.
#[derive(Debug, PartialEq, Eq, Clone, Copy)]
pub struct MyColor {
    r: u8,
    g: u8,
    b: u8,
}

impl PrecalcConst for MyColor {
    const DEFAULT: Self = MyColor { r: 0, g: 0, b: 0 };
}

Examples

Comparing Modes

Here is a side-by-side comparison of how each mode behaves.

use recuerdame::precalculate;

// 1. Fallback Mode (Default)
#[precalculate(a = -10..=10)] // fallback is implicit
const fn identity_fallback(a: i32) -> i32 { a }

// 2. Option Mode
#[precalculate(a = -10..=10, option)]
const fn identity_opt(a: i32) -> i32 { a }

// 3. Panic Mode
#[precalculate(a = -10..=10, panic)]
const fn identity_panic(a: i32) -> i32 { a }

fn main() {
    // In-range behavior is consistent (except for Option's wrapper)
    assert_eq!(identity_fallback(5), 5);
    assert_eq!(identity_opt(5), Some(5));
    assert_eq!(identity_panic(5), 5);

    // Out-of-range behavior differs
    assert_eq!(identity_fallback(20), 20); // falls back to original function
    assert_eq!(identity_opt(20), None);
    // identity_panic(20) would panic!
}

Using Custom Types

This example uses the custom MyColor struct defined in the Return Types section.

use recuerdame::{precalculate, PrecalcConst};

#[derive(Debug, PartialEq, Eq, Clone, Copy)]
pub struct MyColor { r: u8, g: u8, b: u8 }

impl PrecalcConst for MyColor {
    const DEFAULT: Self = MyColor { r: 0, g: 0, b: 0 };
}

#[precalculate(val = 0..=2)]
const fn get_primary_color(val: u8) -> MyColor {
    match val {
        0 => MyColor { r: 255, g: 0, b: 0 },
        1 => MyColor { r: 0, g: 255, b: 0 },
        _ => MyColor { r: 0, g: 0, b: 255 },
    }
}

// The lookup works perfectly with custom types
assert_eq!(get_primary_color(0), MyColor { r: 255, g: 0, b: 0 });

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, use panic. If out-of-range inputs are possible and need to be handled explicitly, use option.

  • 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 fn Required: The macro can only be applied to functions marked as const fn.

  • Integer Arguments Required: The function arguments must be integer primitives.

License

This project is licensed under the MIT License.

Dependencies

~165–580KB
~14K SLoC