SignalStream & PropertyStream shouldn't keep ref to parent Proxy

[zeenix]

The following discussion from !408 should be addressed:

• [ ] @danieldg started a discussion: (+3 comments)

  This results in a PropertyStream that can outlive the parent Proxy, which is not what we want because the task that feeds the stream only lives as long as the proxy. I should have been more clear with my prior comment, which was suggesting the prototype be:

      pub async fn receive_property_changed<'p, T>(
          &'p self,
          name: &'p str,
      ) -> PropertyStream<'p, T>

[zeenix]

In GitLab by @danieldg on Nov 5, 2021, 21:35

The simplest solution is to have both streams hold an owned Proxy instead of a reference to one.

[zeenix]

In GitLab by @danieldg on Nov 5, 2021, 21:35

marked the checklist item @danieldg started a discussion: (+3 comments) as completed

[zeenix]

In GitLab by @danieldg on Nov 5, 2021, 21:36

marked the checklist item @danieldg started a discussion: (+3 comments) as incomplete

[zeenix]

yeah, looking into that.

[zeenix]

mentioned in commit bff9dcfad143dc54cbdfb6a2faaa2905014127d1