Enforce constraints on MemoryTracker classes

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Integration
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      We should make sure that the memory tracker classes have some constraints in place the give us confidence that they're working right. 
      MemoryUsageTracker and SimpleMemoryUsageTracker  similar to this example here.

      • delete the copy constructor, and the copy assignment constructor
      • delete the move constructor too, if it isn't used at all
      • Anything else that makes sense

      There are probably already places where we violate those constraints, they can be addressed as part of this ticket.

            Assignee:
            Aaron Baruch
            Reporter:
            Chris Wolff
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: