Yes, when I wrote: >but also the value is trivial enough that it doesn't matter when it's destroyed or what it does when it's destroyed" that precludes the va

Yes, when I wrote: >but also the value is trivial enough that it doesn't matter when it's destroyed or what it does when it's destroyed" that precludes the value from having other refcounting pointers that could then create cycles and leak.