ExecutorFuture::thenRunOn should not getAsync() on same executor

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Works as Designed
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Service Arch 2019-08-12
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The current thenRunOn() is a strict passthru to SemiFuture::thenRunOn(). If we compare against the _exec member, then we can potentially continue to run inline if the future is already on that executor.

            Assignee:
            Benjamin Caimano (Inactive)
            Reporter:
            Benjamin Caimano (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: