Does caching callbacks in a struct component create a reference cycle?

[zstewar1]

Many callbacks don't require state specific to a particular call to view, so it makes sense to store them on a component, similar to use_callback in the functional component case, so that they compare equal and don't trigger props changes in children.

I have been doing this by declaring a field in the struct component of type Callback, and then populating it during create. However I know that Callback works by cloning the Scope and moving it into the Callback, so my struct will then contain an owned reference to its own Scope.

My question is, does storing a clone of the component's Scope within a struct component create a reference cycle and prevent the struct component from being destructed, or is storing a component's own scope within it normal/acceptable.

E.g.

pub struct MyComponent {
   cached_callback: Callback<()>,
}

impl Component for MyComponent {
    // ...
    fn create(ctx: &Context<Self>) -> Self {
        Self {
            cached_callback: ctx.link().callback(|()| SomeMessage),
        }
    }
}