Introduce an IndexedHashMap
, which has constant time lookup and stable iteration order.
#864
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Introduce an
IndexedHashMap
, which has constant time lookup and stable iteration order.This change introduces an
IndexedHashMap
, which has O(1) lookup but stable iteration order. Under the hood, this is just a combination of aabsl::flat_hash_map
from key to index and astd::vector
containing the values. This can't really use a standard C++ interface due to the key and the value not being co-located, but we can provide a sensible alternative map interface for it.