Module lair_keystore_api::dependencies::sodoken::buffer
source · Expand description
Additional types related to working with buffers.
The main sodoken buffer documentation is at the crate-level. You probably don’t need to reference the types here unless you are implementing a custom sodoken buffer type.
Structs§
- This read-only buffer type is mem_locked. Use this for passwords / private keys, etc, but NOT everything, locked memory is a finite resource.
- This sized read-only buffer type is mem_locked. Use this for passwords / private keys, etc, but NOT everything, locked memory is a finite resource.
- This writable buffer type is mem_locked. Use this for passwords / private keys, etc, but NOT everything, locked memory is a finite resource.
- This writable buffer type is mem_locked. Use this for passwords / private keys, etc, but NOT everything, locked memory is a finite resource.
- An extend guard, indicating we have gained access to extend the buffer.
- A read guard, indicating we have gained access to read buffer memory.
- A read guard, indicating we have gained access to read sized buffer memory.
- A write guard, indicating we have gained access to write buffer memory.
- A write guard, indicating we have gained access to write sized buffer memory.
Traits§
- A buffer that may be appended to and may or may not be mem_locked.
- A readable buffer that may or may not be mem_locked.
- A sized readable buffer that may or may not be mem_locked.
- A writable buffer that may or may not be mem_locked.
- A writable buffer that may or may not be mem_locked.
- Indicates we can append bytes without pre-initializing them.
- Indicates we can dereference an item as a readable byte array.
- Indicates we can dereference a sized item as a readable byte array.
- Indicates we can dereference an item as a mutable byte array.
- Indicates we can dereference a sized item as a mutable byte array.