[CQF] Fix object ownership issues of data members of the Memo class

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 6.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • QO 2022-10-03, QE 2022-10-17
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The Memo class contains the following members: const reference to Metadata and const DebugInfo. Both of these cause the Memo class to not be copy assignable. This has many subtle downstream consequences, for example, OptPhaseManager's implicit move constructor leaves phaseManager.memo.metadata as a dangling reference. See this thread for more info.

      This ticket tracks work to rationalize and implement what the ownership model of these members should be in order to allow the OptPhaseManager to be properly moveable and the Memo copyable and movable.

            Assignee:
            Svilen Mihaylov (Inactive)
            Reporter:
            Ben Shteinfeld
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: