tag | ee6ecda9577bc1b7f49ea94357683e47303eb3c2 | |
---|---|---|
tagger | The Android Open Source Project <initial-contribution@android.com> | Mon May 06 21:48:02 2024 -0700 |
object | 10b511f6f87f4a97ec34f9762583b9526df55b67 |
Android platform 14.0.0 release 7
commit | 10b511f6f87f4a97ec34f9762583b9526df55b67 | [log] [tgz] |
---|---|---|
author | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Fri Mar 10 02:20:28 2023 +0000 |
committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Fri Mar 10 02:20:28 2023 +0000 |
tree | 6a58b521516f9270099a4bb3a83d40401f935e16 | |
parent | a2bee9015d0cc0267102438fe234478a8cac7f55 [diff] | |
parent | fd8a2f26a4f05ab2022d50f7bc6d60386ec6e732 [diff] |
Snap for 9719949 from fd8a2f26a4f05ab2022d50f7bc6d60386ec6e732 to udc-release Change-Id: I269b000f96b481283d7ccb67d8bcfe3f7357c6cf
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. occupied.to_back(); occupied.into_mut() } 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 .raw_entry_mut() .from_key(&key) .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.