-
Notifications
You must be signed in to change notification settings - Fork 545
CXX-3232 add bsoncxx v1 declarations #1412
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
b52a537
to
07f460e
Compare
07f460e
to
98521ae
Compare
if (("$ret" & 0x03)); then # ABIDIFF_ERROR (1) | ABIDIFF_USAGE_ERROR (2) | ||
echo "abidiff error" >&2 | ||
exit 1 | ||
elif (("$ret" & 0x08)); then # ABIDIFF_ABI_INCOMPATIBLE_CHANGE (8). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Per abidiff docs:
The exit code of the abidiff command is either
0
if the ABI of the binaries being compared are equal, or non-zero if they differ or if the tool encountered an error. In the later case, the exit code is a 8-bits-wide bit field in which each bit has a specific meaning.
This PR introduces the first exported v1 ABI symbol: bsoncxx::v1::exception::~exception()
. This new symbol triggered a non-zero exit code of ABIDIFF_ABI_CHANGE (4)
, which was incorrectly handled as incompatibility/failure. The script is updated to distinguish the individual error codes appropriately: we only care about incompatible changes. Compatible changes (such as this) will still be included in the resulting abidiff report.
std::is_trivially_copy_constructible<T>, | ||
std::is_trivially_copy_assignable<T>> {}; | ||
struct is_semitrivial | ||
// https://gcc.gnu.org/onlinedocs/gcc-4.9.0/libstdc++/manual/manual/status.html |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unfortunately, GCC 4.X (used by RHEL 7) does not support the std::is_trivially_*
type traits. Special-case this compiler version by simply assuming this property to be true (we have plenty of true coverage with other compilers and compiler versions on other platforms).
static_assert( | ||
is_nothrow_moveable<view::const_iterator>::value, | ||
"bsoncxx::v1::document::view::const_iterator must be nothrow moveable"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Despite v1::document::view
being semitrivial, its iterator is only nothrow moveable due to its internal v1::element::view
data member.
static_assert( | ||
is_nothrow_moveable<view::const_iterator>::value, | ||
"bsoncxx::v1::array::view::const_iterator must be nothrow moveable"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Despite v1::array::view
being semitrivial, its iterator is only nothrow moveable due to its internal v1::element::view
data member.
namespace bsoncxx { | ||
namespace v1 { | ||
|
||
exception::~exception() = default; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the key function for the bsoncxx::v1::exception
class and the first v1 ABI symbol (along with the vtable) to be exported by the bsoncxx library. 🎉
Although this is meant a declarations-only PR, this definition is required to support successful builds with MSVC, as otherwise:
error LNK2019: unresolved external symbol "public: virtual __cdecl bsoncxx::v1::exception::~exception(void)" (??1exception@v1@bsoncxx@@UEAA@XZ) referenced in function "public: virtual void * __cdecl bsoncxx::v1::exception::`vector deleting destructor'(unsigned int)" (??_Eexception@v1@bsoncxx@@UEAAPEAXI@Z)
deleter_type const& get_deleter() const { | ||
return _data.get_deleter(); | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A non-const .get_deleter()
is deliberately not provided to prevent "desync" of the deleter from the associated BSON binary data. Read-only access is nevertheless essential to support inspection of the type of underlying deleter, such as for v_noabi compatibility (e.g. "Is this deleter compatible with v_noabi::document::value::deleter_type
?"). This will be explored in CXX-3234 (v_noabi refactor).
/// | ||
/// Implicitly convert to `this->view()`. | ||
/// | ||
/* explicit(false) */ operator v1::document::view() const { | ||
return this->view(); | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Asymmetry: value -> view
is implicit, but view -> value
is explicit.
/// | ||
/// Implicitly convert to `this->view()`. | ||
/// | ||
/* explicit(false) */ operator v1::types::view() const { | ||
return this->view(); | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Asymmetry: value -> view
is implicit, but view -> value
is explicit.
/// | ||
/// Return a view of the BSON binary data as a document. | ||
/// | ||
v1::document::view view() const { | ||
return {_data.get(), _length}; | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All member functions below are defined in terms of v1::document::view
, including error codes and Doxygen documentation.
Important
The new "invalid" state of a v1::document::view
allows this conversion to be well-defined even when a value
is default-initialized (_data.get() == nullptr
).
class value {}; | ||
class value { | ||
private: | ||
v1::document::value _value; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All behavior for this class is defined in terms of v1::document::value
or v1::array::view
, including error codes and Doxygen documentation.
/// @note This iterator almost satisfies Cpp17ForwardIterator, but `std::iterator_traits<T>::reference` is defined as | ||
/// `value_type`, similar to `std::vector<bool>::iterator` and `std::istreambuf_iterator<T>`. Therefore, this iterator | ||
/// only fully satisfies Cpp17InputIterator. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Update: renamed Legacy
-> Cpp17
for consistency with standard spec for C++20 and newer (by P0896R4; cppreference still uses "Legacy", a leftover from when the C++20 spec was still being drafted) + restoring this comment due to the associated changes of the prior comment being lost by GitHub.
The v1 ABI interfaces address and clarify several issues with iterators that were identified during work on CXX-3082:
- Missing const qualifiers on multiple member functions, e.g.
auto const iter = doc.begin(); use(*iter);
is ill-formed (?!). iterator_category = std::forward_iterator_tag
despite not actually satisfying the requirements of LegacyForwardIterator:- e.g. does not satisfy
it: const_iterator
->*it -> T const&
. - e.g. does not satisfy
a == b
->std::addressof(*a) == std::addressof(*b)
.
- e.g. does not satisfy
- Operations on an end iterator behavior, such as deference yielding an invalid element and increment yielding another end iterator, are
underdocumentednot documented at all.
v1::document::view::const_iterator
(and v1::array::view::const_iterator
) addresses all these issues by ensuring it properly satisfies and declares itself to be a LegacyInputIterator instead (even though it may provide some features of a LegacyForwardIterator).
Resolves CXX-3232. Followup to #1318, #1401, and #1402.
This is 2 out of an estimated 7 major PRs which in total are expected to resolve CXX-2745.
This PR introduces the very first set of v1 ABI exported symbols. 🎉
... only because MSVC complains otherwise. The rest will come as planned in CXX-3233 (impls).
Due to the volume of changes relative to the equivalent v_noabi interfaces, the bulk of relative changelog (v_noabi -> v1) and rationale for design decisions are documented inline as GitHub comments (coincidentally, exactly 100 comments in total).
In summary, notable changes include:
v1::error
v1::error
with corresponding error category declared inv1::error::category
.source
andtype
are provided as the primary user-facing error code query mechanism when component-specific error codes are not necessary.v1::types::b_*
value
).v1::types::view
value
when applicable.v1::types::value
b_*
is always favored) so eitherb_*
orview
(cheap) is always preferred tovalue
(expensive) when applicable.v1::types::id
constructors are removed in favor ofb_*
and converting constructors.v1::element::view
bool
-based approach to "missing field" diagnostics (CXX-2120).v1::document::view
v1::array::view
v1::document::view
.v1::document::view
(CXX-2118).v1::document::value
v1::document::view
.deleter_type
is now astd::function<T>
instead of a function pointer.to_bson
andfrom_bson
are now properly constrained.v1::array::value
v1::document::value
.v1::document::value
(CXX-2118).