Struct TestDBKeysAsyncSendBuilder

pub struct TestDBKeysAsyncSendBuilder<'a, K, IterBuilder_: for<'this> FnOnce(&'this mut RwLockReadGuard<'a, BTreeMap<Vec<u8>, Vec<u8>>>) -> Pin<Box<dyn Future<Output = Iter<'this, Vec<u8>, Vec<u8>>> + Send + 'this>>> {
    pub rows: RwLockReadGuard<'a, BTreeMap<Vec<u8>, Vec<u8>>>,
    pub iter_builder: IterBuilder_,
    pub phantom: PhantomData<K>,
}

A more verbose but stable way to construct self-referencing structs. It is comparable to using StructName { field1: value1, field2: value2 } rather than StructName::new(value1, value2). This has the dual benefit of making your code both easier to refactor and more readable. Call build() to construct the actual struct. The fields of this struct should be used as follows:

Field	Suggested Use
rows	Directly pass in the value this field should contain
iter_builder	Use a function or closure: (rows: &mut _) -> iter: _
phantom	Directly pass in the value this field should contain

Fields

rows: RwLockReadGuard<'a, BTreeMap<Vec<u8>, Vec<u8>>>

iter_builder: IterBuilder_

phantom: PhantomData<K>

Implementations

impl<'a, K, IterBuilder_: for<'this> FnOnce(&'this mut RwLockReadGuard<'a, BTreeMap<Vec<u8>, Vec<u8>>>) -> Pin<Box<dyn Future<Output = Iter<'this, Vec<u8>, Vec<u8>>> + Send + 'this>>> TestDBKeysAsyncSendBuilder<'a, K, IterBuilder_>

pub async fn build(self) -> TestDBKeys<'a, K>

Calls TestDBKeys::new() using the provided values. This is preferable over calling new() directly for the reasons listed above.