// Note: the RealmBuilder functions below this line all forward to the implementations in
// SubRealmBuilder. It would be easier to hold these definitions in a common trait that both
// structs implemented, but then anyone using RealmBuilder would have to use the trait
// regardless of if they want sub-realm support or not. This approach, which slightly more
// tedious, is slightly more convenient for users (one less import they have to remember).
the RealmBuilder functions below this line all forward to the implementations in
SubRealmBuilder. It would be easier to hold these definitions in a common trait that both
structs implemented, but then anyone using RealmBuilder would have to use the trait
regardless of if they want sub-realm support or not. This approach, which slightly more
tedious, is slightly more convenient for users (one less import they have to remember).
the RealmBuilder functions below this line all forward to the implementations in SubRealmBuilder . It would be easier to hold these definitions in a common trait that both structs implemented but then anyone using RealmBuilder would have to use the trait regardless of if they want sub - realm support or not . This approach which slightly more tedious is slightly more convenient for users ( one less import they have to remember ) .
pub async fn add_child_realm(
        &self,
        name: impl Into<String>,
        options: ChildOptions,
    ) -> Result<SubRealmBuilder, Error> {
        self.root_realm.add_child_realm(name, options).await
    }
pub async fn add_child_realm ( & self , name : impl Into < String > , options : ChildOptions , ) -> Result < SubRealmBuilder , Error > { self . root_realm . add_child_realm ( name , options ) . await }
Note: the RealmBuilder functions below this line all forward to the implementations in
SubRealmBuilder.
Note : the RealmBuilder functions below this line all forward to the implementations in SubRealmBuilder .
&self
name
impl Into<String>
options
ChildOptions