4 releases (breaking)

0.4.0 Aug 25, 2022
0.3.0 Aug 25, 2022
0.2.0 Aug 25, 2022
0.1.0 Aug 24, 2022

#1529 in Data structures

Download history 27886/week @ 2024-01-05 31246/week @ 2024-01-12 37570/week @ 2024-01-19 43236/week @ 2024-01-26 40466/week @ 2024-02-02 42227/week @ 2024-02-09 44975/week @ 2024-02-16 42959/week @ 2024-02-23 39927/week @ 2024-03-01 40473/week @ 2024-03-08 42966/week @ 2024-03-15 50973/week @ 2024-03-22 47668/week @ 2024-03-29 56337/week @ 2024-04-05 59534/week @ 2024-04-12 45820/week @ 2024-04-19

217,065 downloads per month
Used in 155 crates (2 directly)

Apache-2.0

47KB
1K SLoC

indexmap-nostd

A no_std compatible indexmap crate (re)implementation.

Note: The indexmap crate already supports to be compiled in no_std environments and it uses hashbrown crate's HashMap under the hood which still requires some sort of randomized initialization. However, some embedded platforms simply cannot provide ways to randomly seed hash maps and similar data structures making code that depends on it susceptible to users (or attackers) that control inputs to those hash maps.

Therefore indexmap-nostd is a (re)implementation of the indexmap crate that replaces the internal use of HashMap with BTreeMap.

Advantages

This crate and its data structures can be used in any embedded no_std environment without the need to provide random seeds for HashMap initialization.

Disadvantages

  • The current implementation of indexmap-nostd focuses on being easy to maintain simple code which trades off efficiency compared to the original indexmap crate. An example of performance regression is that now inserted keys are duplicated.
  • Due to the above point some methods now require additional where bounds. For example IndexMap::insert now requires K: Clone.
  • We are primarily interested in getting this no_std compatible implementation to be working for the wasmparser crate. This means that we primarily provide a subset of the features and API of the original indexmap crate and might not be interested in adding features that we do not need for this use case that are also hard to implement or maintain.

Dependencies

~185KB