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

Reconsider usage of optional<RecordId>

    • Type: Icon: Task Task
    • Resolution: Won't Do
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Execution Team 2022-12-12

      RecordId contains an explicit Null state when created without any data. There are currently usages of RecordId in a boost::optional which means we need to double check the nullability of the given element.

      This ticket is about reconsidering usages of this in favour of a plain RecordId with the Null state to avoid unnecessary wrapping of RecordId into a boost::optional.

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

              Created:
              Updated:
              Resolved: