storage_api
| Crates.io | storage_api |
| lib.rs | storage_api |
| version | |
| source | src |
| created_at | 2025-04-13 10:28:51.304604+00 |
| updated_at | 2025-04-23 01:51:26.736781+00 |
| description | Implementation of the Storage API, a better version of Allocator |
| homepage | |
| repository | https://github.com/HomelikeBrick42/StorageAPI |
| max_upload_size | |
| id | 1631711 |
| 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 |
(HomelikeBrick42)
documentation
README
Storage API
This is an implementation of the Storage API, a better version of the Allocator API, and data structures made for them including
BoxVecString
How is it better than Allocator?
Storages have an associated Handle type so allocations dont need to be represented by a pointer, which allows Storages to allocate from a buffer they store inline
Instead of having Vec and ArrayVec as 2 seperate data structures they can be merged together, only using different Storages