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

Investigate Future::onCompletion/onError API improvement

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Server Programmability

      With SERVER-86355 we discovered that we were mistakenly swallowing an error within the callback function used for onCompletion. This lead to check if there are other places where we were swallowing errors.

      Adding !(future_details::isCallableExactR<void, Func, StatusOrStatusWith<T>>) to the concept requirements of onCompletion alone lead us to file SERVER-86398, SERVER-86397 and SERVER-86396 which explored potential misuses of the API.

      This ticket is about considering if we should explore a more strict API so we have to explicitly choose to swallow errors.

            Assignee:
            Unassigned Unassigned
            Reporter:
            jordi.olivares-provencio@mongodb.com Jordi Olivares Provencio
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated: