Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-66036

Improve future validity semantics

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 6.2.0-rc0, 5.0.25
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • Service Arch 2022-05-02, Service Arch 2022-05-16, Service Arch 2022-05-30, Service Arch 2022-06-13, Service Arch 2022-06-27, Service Arch 2022-07-11, Service Arch 2022-07-25, Service Arch 2022-08-08, Service Arch 2022-08-22, Service Arch 2022-09-05, Service Arch 2022-09-19

      This is a follow-up to SERVER-62560.

      Although the concept of validity can reflect whether a Future has access to a SharedState (or an immediate value in the case of an optimization), out of the box there are many cases where futures remain valid(), when using them is not necessarily valid. For example, `get` does not currently invalidate the pointer to the SharedState/set it to nullptr.

            Assignee:
            matt.diener@mongodb.com Matt Diener (Inactive)
            Reporter:
            matt.diener@mongodb.com Matt Diener (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: