#key-value #order #pair #user #container #hash-key

no-std hashlink

HashMap-like containers that hold their key-value pairs in a user controllable order

16 releases (8 breaking)

0.9.1 May 12, 2024
0.9.0 Jan 9, 2024
0.8.4 Aug 28, 2023
0.8.3 Jun 11, 2023
0.3.0 Jul 12, 2019

#18 in Data structures

Download history 521303/week @ 2024-02-21 515568/week @ 2024-02-28 529780/week @ 2024-03-06 499891/week @ 2024-03-13 510745/week @ 2024-03-20 462993/week @ 2024-03-27 518766/week @ 2024-04-03 505303/week @ 2024-04-10 519538/week @ 2024-04-17 546359/week @ 2024-04-24 526376/week @ 2024-05-01 534299/week @ 2024-05-08 565177/week @ 2024-05-15 566826/week @ 2024-05-22 626563/week @ 2024-05-29 498360/week @ 2024-06-05

2,359,409 downloads per month
Used in 2,123 crates (55 directly)



hashlink -- HashMap-like containers that hold their key-value pairs in a user controllable order

Build Status Latest Version API Documentation

This crate is a fork of linked-hash-map that builds on top of hashbrown to implement more up to date versions of LinkedHashMap LinkedHashSet, and LruCache.

One important API change is that when a LinkedHashMap is used as a LRU cache, it allows you to easily retrieve an entry and move it to the back OR produce a new entry at the back without needlessly repeating key hashing and lookups:

let mut lru_cache = LinkedHashMap::new();
let key = "key".to_owned();
// Try to find my expensive to construct and hash key
let _cached_val = match lru_cache.raw_entry_mut().from_key(&key) {
    RawEntryMut::Occupied(mut occupied) => {
        // Cache hit, move entry to the back.
    RawEntryMut::Vacant(vacant) => {
        // Insert expensive to construct key and expensive to compute value,
        // automatically inserted at the back.
        vacant.insert(key.clone(), 42).1

Or, a simpler way to do the same thing:

let mut lru_cache = LinkedHashMap::new();
let key = "key".to_owned();
let _cached_val = lru_cache
    .or_insert_with(|| (key.clone(), 42));

This crate contains a decent amount of unsafe code from handling its internal linked list, and the unsafe code has diverged quite a lot from the original linked-hash-map implementation. It currently passes tests under miri and sanitizers, but it should probably still receive more review and testing, and check for test code coverage.


There is a huge amount of code in this crate that is copied verbatim from linked-hash-map and hashbrown, especially tests, associated types like iterators, and things like Debug impls.


This library is licensed the same as linked-hash-map and hashbrown, it is licensed under either of:

at your option.


~24K SLoC