OpObserverRegistry doesn't use input opAccumulator

XMLWordPrintableJSON

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

      The methods that take in OpStateAccumulator all create another OpStateAccumulator internally whether the input OpStateAccumulator is null (e.g. here and here). 

            Assignee:
            Moustafa Maher
            Reporter:
            Cheahuychou Mao
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: