vec-btree-map
| Crates.io | vec-btree-map |
| lib.rs | vec-btree-map |
| version | |
| source | src |
| created_at | 2023-12-08 11:01:20.021788 |
| updated_at | 2024-11-24 10:37:56.511727 |
| description | Basically just a sorted Vec that can be used as a HashMap |
| homepage | |
| repository | https://github.com/jaycefayne/vec-btree-map |
| max_upload_size | |
| id | 1061914 |
| Cargo.toml error: | TOML parse error at line 17, column 1 | 17 | autolib = false | ^^^^^^^ unknown field `autolib`, expected one of `name`, `version`, `edition`, `authors`, `description`, `readme`, `license`, `repository`, `homepage`, `documentation`, `build`, `resolver`, `links`, `default-run`, `default_dash_run`, `rust-version`, `rust_dash_version`, `rust_version`, `license-file`, `license_dash_file`, `license_file`, `licenseFile`, `license_capital_file`, `forced-target`, `forced_dash_target`, `autobins`, `autotests`, `autoexamples`, `autobenches`, `publish`, `metadata`, `keywords`, `categories`, `exclude`, `include` |
| size | 0 |
(JayceFayne)
documentation
README
vec-btree-map 
Basically just a sorted Vec that can be used as a HashMap.
Why?
This library is meant for building data structures that you iterate over a lot. Why not just use a HashMap? Iterating over a HashMap is slow and the iteration order is not guaranteed to be stable.
Contributing
If you find any errors or just want to add a new feature feel free to submit a PR.