Closed NinaRanns closed 2 years ago
I thoroughly reviewed this PR before it was submitted. It is good for merging.
Copied this as Bloomberg internal PR 2755
I thoroughly reviewed this PR before it was submitted. It is good for merging.
Merging where? master
??
I think there is a disconnect between what we think is "ready for merge". "Ready for merge" would suggest it has been built and tested our production platforms. A cursory scan of the changes suggests a few things to do before merge:
This has been tested on several other C++11 compilers at Bloomberg (Linux gcc and clang, MacOS Clang, and MSVC 2015). Merging is, of course at Bloomberg's discretion. Work is ongoing to make this component completely BDE compliant, including support for the C++03 compilers. It probably makes sense, therefore, to delay merging until that work is complete.
Closing. bsl::optional, a version of this change-set, was merged to our master branch a year ago or so.
P2047 'An allocator-aware optional type'
C++11 Implementation of P2047 'An allocator-aware optional type'. The implementation differs from the paper in a couple of ways (bsl::allocator is used instead of pmr::polymorphic_allocator, value_or is disabled until the decision is made on how to handle compilers in which copy elision isn't guaranted).
New tests specific to bsl::optional have been implemented.
C++03 support is not implemented yet.