Our great sponsors
-
the map member used for the lookups is a tsl::hopscotch_map (https://github.com/Tessil/hopscotch-map), which is a proper hash map. so it seems to be the latter, that the API is wrong, but from what I can tell it is only a wrongly named class. i don't see where the API makes guarantees about iteration order, which is where the implementation difference would be noticeable (beyond performance for lookup).
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
NOTE:
The number of mentions on this list indicates mentions on common posts plus user suggested alternatives.
Hence, a higher number means a more popular project.
Related posts
- How to create std::map that preserves the order of insertion just using standard C++?
- What’s the fastest doubly linked list out there?
- Any suggestions for resources to optimize for memory allocation/reallocation?
- Fibonacci Hashing: An Optimization the World Forgot (Better Than Integer Modulo)
- Use PEGTL to remove my clunky homemade parser