5 releases

0.1.4 Jul 21, 2020
0.1.3 Jun 7, 2018
0.1.2 Feb 24, 2018
0.1.1 Dec 4, 2017
0.1.0 Oct 25, 2017

#72 in Data structures

Download history 88076/week @ 2024-06-18 89113/week @ 2024-06-25 88756/week @ 2024-07-02 95618/week @ 2024-07-09 102999/week @ 2024-07-16 92952/week @ 2024-07-23 94234/week @ 2024-07-30 111353/week @ 2024-08-06 107606/week @ 2024-08-13 111719/week @ 2024-08-20 102649/week @ 2024-08-27 106767/week @ 2024-09-03 93017/week @ 2024-09-10 92959/week @ 2024-09-17 94863/week @ 2024-09-24 89815/week @ 2024-10-01

389,926 downloads per month
Used in 352 crates (37 directly)

Apache-2.0

59KB
919 lines

linked_hash_set crates.io Documentation

This library provides an hashed set with predictable iteration order, based on the insertion order of elements. It is implemented as a linked_hash_map::LinkedHashMap where the value is (), in a similar way as HashSet is implemented from HashMap in stdlib.

Comparison with std HashSet

General usage is very similar to a traditional hashed set, but this structure also maintains insertion order.

Compared to HashSet, a LinkedHashSet uses an additional doubly-linked list running through its entries. As such methods front(), pop_front(), back(), pop_back() and refresh() are provided.

Comparison with IndexSet

Compared to indexmap::IndexSet, while both maintain insertion order a LinkedHashSet uses a linked list allowing performant removals that don't affect the order of the remaining elements. However, when this distinction is unimportant indexmap should be the faster option.

Example

let mut set = linked_hash_set::LinkedHashSet::new();
assert!(set.insert(234));
assert!(set.insert(123));
assert!(set.insert(345));
assert!(!set.insert(123)); // Also see `insert_if_absent` which won't change order

assert_eq!(set.into_iter().collect::<Vec<_>>(), vec![234, 345, 123]);

Minimum supported rust compiler

This crate is maintained with latest stable rust.

Dependencies

~215KB