Details
-
New Feature
-
Resolution: Unresolved
-
Major - P3
-
None
-
None
-
Service Arch
-
Fully Compatible
Description
Originally this ticket was about using std::optional where possible, and boost::optional elsewhere. The idea of this polyfill was we could avoid including the boost headers in many places if the system provides a std::optional (from std::experimental or similar). After some investigation, the ticket is now about replacing our use of boost::optional with std::optional entirely.
Attachments
Issue Links
- related to
-
SERVER-68121 clang-tool boost::optional -> std::optional migration
-
- Backlog
-
-
SERVER-68246 change calls to `boost::optional` members `is_initialized` and `get` (via clang-tidy)
-
- Closed
-