#map #duration #no-std #timed-map

no-std timed-map

Lightweight map implementation that supports expiring entries and fully compatible with both std and no_std environments

16 stable releases

1.3.2 Apr 19, 2025
1.3.1 Apr 14, 2025
1.3.0 Jan 22, 2025
1.1.1 Nov 4, 2024
0.1.0 Oct 20, 2024

#130 in Data structures

Download history 920/week @ 2025-01-04 1140/week @ 2025-01-11 877/week @ 2025-01-18 749/week @ 2025-01-25 1005/week @ 2025-02-01 1103/week @ 2025-02-08 972/week @ 2025-02-15 941/week @ 2025-02-22 820/week @ 2025-03-01 499/week @ 2025-03-08 746/week @ 2025-03-15 740/week @ 2025-03-22 687/week @ 2025-03-29 592/week @ 2025-04-05 850/week @ 2025-04-12 702/week @ 2025-04-19

2,960 downloads per month

MIT license

49KB
863 lines

timed-map

Lightweight map implementation that supports expiring entries and fully compatible with both std and no_std environments.

TimedMap allows storing key-value pairs with optional expiration times. Expiration is handled by an implementation of the Clock trait, which abstracts time handling for no_std environments.

When std feature is enabled (which is the default case), Clock trait is handled automatically from the crate internals with std::time::SystemTime.

Basic Usage:

In std environments:

use timed_map::TimedMap;
use std::time::Duration;

let mut map = TimedMap::new();

map.insert_expirable(1, "expirable value", Duration::from_secs(60));
assert_eq!(map.get(&1), Some(&"expirable value"));
assert!(map.get_remaining_duration(&1).is_some());

map.insert_constant(2, "constant value");
assert_eq!(map.get(&2), Some(&"constant value"));
assert!(map.get_remaining_duration(&2).is_none());

In no_std environments:

use core::time::Duration;
use timed_map::{Clock, TimedMap};

struct CustomClock;

impl Clock for CustomClock {
    fn elapsed_seconds_since_creation(&self) -> u64 {
    // Hardware-specific implementation to measure the elapsed time.
        0 // placeholder
    }
}

let clock = CustomClock;
let mut map = TimedMap::new(clock);

map.insert_expirable(1, "expirable value", Duration::from_secs(60));
assert_eq!(map.get(&1), Some(&"expirable value"));
assert!(map.get_remaining_duration(&1).is_some());

map.insert_constant(2, "constant value");
assert_eq!(map.get(&2), Some(&"constant value"));
assert!(map.get_remaining_duration(&2).is_none());

Advanced Usage & Tuning:

Customizing the Internal Map

By default, TimedMap uses BTreeMap to store data, but you can switch to FxHashMap or HashMap.

This is only available on std environments.

use timed_map::{MapKind, TimedMap};

let mut map = TimedMap::new_with_map_kind(MapKind::FxHashMap);

Manual Expiration Control

To have fully control over expired entries, use the *_unchecked functions and drop_expired_entries to handle expiration manually. This can boost performance by running expiration logic only when it's necessary to maximize the performance.

let mut map = TimedMap::new();

map.insert_expirable_unchecked(1, "expirable value", Duration::from_secs(60));
assert_eq!(map.get_unchecked(&1), Some(&"expirable value"));

map.insert_constant_unchecked(2, "constant value");
assert_eq!(map.get_unchecked(&2), Some(&"constant value"));

map.drop_expired_entries();

Setting Expiration Check Frequency

In cases where inserts are frequent, expiration_tick_cap can be set to control how often expired entries are removed. For instance, if there are 100 inserts per second, setting expiration_tick_cap to 100 will trigger the expiration check every 100 inserts which will reduce the expiration logic overhead significantly.

use timed_map::TimedMap;

let mut map = TimedMap::new().expiration_tick_cap(500);

Dependencies

~0–250KB