pub fn unique_key(&self) -> UniqueKey {
        let mut key = self.relative_moniker.iter().cloned().collect::<Vec<_>>();
        if let Some(instance_id) = &self.instance_id {
            key.push(instance_id.clone())
        }
        key.into()
    }
/// In V1, a component topology is able to produce two components with
/// the same relative moniker. Because of this, we must, in some cases,
/// differentiate these components using instance ids. The unique key
/// is conceptually a relative moniker which preserves instance ids.
In V1, a component topology is able to produce two components with
the same relative moniker. Because of this, we must, in some cases,
differentiate these components using instance ids. The unique key
is conceptually a relative moniker which preserves instance ids.
In V1 a component topology is able to produce two components with the same relative moniker . Because of this we must in some cases differentiate these components using instance ids . The unique key is conceptually a relative moniker which preserves instance ids .
pub fn unique_key(&self) -> UniqueKey {
        let mut key = self.relative_moniker.iter().cloned().collect::<Vec<_>>();
        if let Some(instance_id) = &self.instance_id {
            key.push(instance_id.clone())
        }
        key.into()
    }
pub fn unique_key ( & self ) -> UniqueKey { let mut key = self . relative_moniker . iter ( ) . cloned ( ) . collect :: < Vec < _ > > ( ) ; if let Some ( instance_id ) = & self . instance_id { key . push ( instance_id . clone ( ) ) } key . into ( ) }
In V1, a component topology is able to produce two components with
the same relative moniker.
In V1 a component topology is able to produce two components with the same relative moniker .
&self
&self