Struct VisibilityAsyncSendTryBuilder 

pub struct VisibilityAsyncSendTryBuilder<PublicFieldBuilder_: for<'this> FnOnce(&'this Box<i32>) -> Pin<Box<dyn Future<Output = Result<&'this i32, Error_>> + Send + 'this>>, PubCrateFieldBuilder_: for<'this> FnOnce(&'this Box<i32>) -> Pin<Box<dyn Future<Output = Result<&'this i32, Error_>> + Send + 'this>>, Error_> {
    pub private_field: Box<i32>,
    pub public_field_builder: PublicFieldBuilder_,
    pub pub_crate_field_builder: PubCrateFieldBuilder_,
}

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 try_build() or try_build_or_recover() to construct the actual struct. The fields of this struct should be used as follows:

Field	Suggested Use
private_field	Directly pass in the value this field should contain
public_field_builder	Use a function or closure: (private_field: &_) -> Result<public_field: _, Error_>
pub_crate_field_builder	Use a function or closure: (private_field: &_) -> Result<pub_crate_field: _, Error_>

Fields

private_field: Box<i32>

public_field_builder: PublicFieldBuilder_

pub_crate_field_builder: PubCrateFieldBuilder_

Implementations

impl<PublicFieldBuilder_: for<'this> FnOnce(&'this Box<i32>) -> Pin<Box<dyn Future<Output = Result<&'this i32, Error_>> + Send + 'this>>, PubCrateFieldBuilder_: for<'this> FnOnce(&'this Box<i32>) -> Pin<Box<dyn Future<Output = Result<&'this i32, Error_>> + Send + 'this>>, Error_> VisibilityAsyncSendTryBuilder<PublicFieldBuilder_, PubCrateFieldBuilder_, Error_>

pub async fn try_build(self) -> Result<Visibility, Error_>

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

pub async fn try_build_or_recover(self) -> Result<Visibility, (Error_, Heads)>

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