| Crates.io | typed-index-collections |
| lib.rs | typed-index-collections |
| version | 3.3.0 |
| created_at | 2020-07-13 16:53:15.893861+00 |
| updated_at | 2025-05-05 11:10:23.895317+00 |
| description | Typed index version of Rust slice and Vec containers |
| homepage | |
| repository | https://github.com/zheland/typed-index-collections |
| max_upload_size | |
| id | 264743 |
| size | 271,334 |
The typed-index-collections crate provides TiSlice and TiVec
structs that are typed index versions of the Rust slice and
std::vec::Vec types.
The extensive use of slices and vectors instead of references and smart pointers might be useful for optimization, Data-Oriented Design and when using Struct of Arrays. But when dealing with a bunch of slices and vectors it is easy to accidentally use the wrong index, which is a common source of bugs.
This crate provides TiSlice<K, V> and
TiVec<K, V> containers that can be indexed only by the
specified index type K. These containers are only wrappers around
the slice primitive [V] and the container
std::vec::Vec<V>. Crate containers mirror the stable
API of the matched Rust containers and forward to them as much as possible.
TiSlice and TiVec can be easily converted to matched Rust containers
and back using From, Into, AsRef and AsMut traits.
Also, they expose raw property with the original data type.
Containers only require the index to implement
From<usize> and Into<usize> traits
that can be easily done with derive_more crate and
#[derive(From, Into)].
First, add the following to your Cargo.toml:
[dependencies]
typed-index-collections = "3.3.0"
This crate depends on the standard library by default that is useful
for debugging and for some extra functionality.
To use this crate in a #![no_std] context, use default-features = false
in your Cargo.toml as shown below:
[dependencies.typed-index-collections]
version = "3.3.0"
default-features = false
features = ["alloc"]
If you want to use derive_more for
From<usize> and Into<usize> implementation
add it to your Cargo.toml as shown below:
[dependencies]
derive_more = "0.99"
typed-index-collections = "3.3.0"
Simple example with derive_more:
use typed_index_collections::TiVec;
use derive_more::{From, Into};
#[derive(From, Into)]
struct FooId(usize);
let mut ti_vec: TiVec<FooId, usize> = std::vec![10, 11, 13].into();
ti_vec.insert(FooId(2), 12);
assert_eq!(ti_vec[FooId(2)], 12);
If a wrong index type is used, compilation will fail:
use typed_index_collections::TiVec;
use derive_more::{From, Into};
#[derive(From, Into)]
struct FooId(usize);
#[derive(From, Into)]
struct BarId(usize);
let mut ti_vec: TiVec<FooId, usize> = std::vec![10, 11, 13].into();
ti_vec.insert(BarId(2), 12);
// ^^^^^^^^ expected struct `FooId`, found struct `BarId`
assert_eq!(ti_vec[BarId(2)], 12);
// ^^^^^^^^^^^^^^^^ the trait ... is not implemented for `BarId`
Another more detailed example with derive_more:
use typed_index_collections::{TiSlice, TiVec};
use derive_more::{From, Into};
#[derive(Clone, Copy, Debug, From, Into, Eq, PartialEq)]
struct FooId(usize);
#[derive(Clone, Copy, Debug, Eq, PartialEq)]
struct Foo {
value: usize,
}
let first = Foo { value: 1 };
let second = Foo { value: 2 };
let slice_ref = &[first, second][..];
let vec = std::vec![first, second];
let boxed_slice = std::vec![first, second].into_boxed_slice();
let ti_slice_ref: &TiSlice<FooId, Foo> = slice_ref.as_ref();
let ti_vec: TiVec<FooId, Foo> = vec.into();
let ti_boxed_slice: std::boxed::Box<TiSlice<FooId, Foo>> =
boxed_slice.into();
assert_eq!(ti_vec[FooId(1)], second);
assert_eq!(ti_vec.raw[1], second);
assert_eq!(ti_vec.last(), Some(&second));
assert_eq!(ti_vec.last_key_value(), Some((FooId(1), &second)));
assert_eq!(ti_vec.iter_enumerated().next(), Some((FooId(0), &first)));
let _slice_ref: &[Foo] = ti_slice_ref.as_ref();
let _vec: std::vec::Vec<Foo> = ti_vec.into();
let _boxed_slice: std::boxed::Box<[Foo]> = ti_boxed_slice.into();
alloc (implied by std, enabled by default): Enables the Rust alloc
library, enables TiVec type, ti_vec! macro, trait implementations
for Box<TiSlice>, and some TiSlice methods that require
memory allocation.std (enabled by default): Enables alloc feature, the Rust std
library, implements std::io::Write for TiVec and implements
std::io::Read and std::io::Write for TiSlice,serde: Implements Serialize trait for TiSlice and TiVec
containers and Deserialize trait for Box<TiSlice> and
TiVec.bincode: Implements Encode trait for TiSlice and TiVec
containers and Decode and BorrowDecode traits for
Box<TiSlice> and TiVec.typed_index_collection provides a Vec wrapper with a very limited
API. Indices are u32 wrappers, they are not customizable and can only
index a specific type of container.indexed_vec is the closest copy of the IndexVec struct from
librustc_index, but API is also different from standard Rust
std::vec::Vec and it has no typed index slice alternative.index_vec have both slice and std::vec::Vec wrapper and API
closer to standard API. But it implicitly allows you to use usize for
get methods and index expressions that reduce type-safety, and the macro
define_index_type! which is used to generate a newtyped index struct,
implicitly implements a lot of traits that in my opinion would be better
implemented only when necessary using crates intended for this, such as
derive_more.Licensed under either of
at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.