move Future implementation details to a separate header

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.1.10
    • Affects Version/s: None
    • Component/s: Internal Code
    • None
    • Fully Compatible
    • Service Arch 2019-03-25
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      This will also move the implementation details to a separate type which will make it easier to introduce SemiFuture and ExecutorFuture without substantial code duplication.

            Assignee:
            Mathias Stearn
            Reporter:
            Mathias Stearn
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: