Crate heed_types
source ·Expand description
Types that can be used to serialize and deserialize types inside databases.
How to choose the right type to store things in this database? For specific types you can choose:
Strto storestrsUnitto store()typesSerdeBincode,SerdeJson, or [SerdeRmp] to store [Serialize]/[Deserialize] types
Structs
- Describes a slice that must be memory aligned and will be reallocated if it is not.
- Describes a type that must be memory aligned and will be reallocated if it is not.
- A convenient struct made to ignore the type when decoding it.
- Encodable version of
i8 - Encodable version of
i16. - Encodable version of
i32. - Encodable version of
i64. - Encodable version of
i128. - Owns bytes that can be decoded on demand.
- Lazily decode the data bytes, it can be used to avoid CPU intensive decoding before making sure we really need to decode it (e.g. based on the key).
- Describes a
Vecof types that are totally owned (doesn’t hold any reference to the original slice). - Describes a type that is totally owned (doesn’t hold any reference to the original slice).
- Describes an
str. - Encodable version of
u8 - Encodable version of
u16. - Encodable version of
u32. - Encodable version of
u64. - Encodable version of
u128. - Describes a type that is totally borrowed and doesn’t depends on any memory alignment.
- Describes a slice that is totally borrowed and doesn’t depends on any memory alignment.
- Describes the
()type.
Type Aliases
- Describes a slice of bytes
[u8]that is totally borrowed and doesn’t depends on any memory alignment.