Changes imported from Abseil "staging" branch:
- d5a5960a133967e4af02836d304884cd6cbd6e46 Adjusting time tests for flakiness by Gennadiy Civil <misterg@google.com> - ccb8535fdc92c3c99bfa2795e75d3fbdcb134571 Internal-only tweak. by Jorg Brown <jorg@google.com> - 4c03dd9e54bd4645e7e7a8dfb3c590f5b0654884 Fix comment on some C++11 type traits backport. by Xiaoyi Zhang <zhangxy@google.com> - 43cd12d2304464163e33ae932fbb842a869213dd Allow intrinsic int128 to be set for __ppc64__ targets. by Abseil Team <absl-team@google.com> - 789e9c13de67ef3c7ba09c765c3484621897b6bb Update README.md description of 'types' library to be con... by Abseil Team <absl-team@google.com> - 8be10d7683c90b85244ddc67360a7ca2dfffdf01 Update comment on move constructors' noexcept specificati... by Xiaoyi Zhang <zhangxy@google.com> GitOrigin-RevId: d5a5960a133967e4af02836d304884cd6cbd6e46 Change-Id: I743efee47b9e65f46a44d9ab80ccd62cfd0c1301
This commit is contained in:
parent
cc4bed2d74
commit
d732f2014b
7 changed files with 56 additions and 16 deletions
|
@ -124,9 +124,24 @@ class InlinedVector {
|
|||
InlinedVector(const InlinedVector& v);
|
||||
InlinedVector(const InlinedVector& v, const allocator_type& alloc);
|
||||
|
||||
// This move constructor does not allocate and only moves the underlying
|
||||
// objects, so its `noexcept` specification depends on whether moving the
|
||||
// underlying objects can throw or not. We assume
|
||||
// a) move constructors should only throw due to allocation failure and
|
||||
// b) if `value_type`'s move constructor allocates, it uses the same
|
||||
// allocation function as the `InlinedVector`'s allocator, so the move
|
||||
// constructor is non-throwing if the allocator is non-throwing or
|
||||
// `value_type`'s move constructor is specified as `noexcept`.
|
||||
InlinedVector(InlinedVector&& v) noexcept(
|
||||
absl::allocator_is_nothrow<allocator_type>::value ||
|
||||
std::is_nothrow_move_constructible<value_type>::value);
|
||||
|
||||
// This move constructor allocates and also moves the underlying objects, so
|
||||
// its `noexcept` specification depends on whether the allocation can throw
|
||||
// and whether moving the underlying objects can throw. Based on the same
|
||||
// assumptions above, the `noexcept` specification is dominated by whether the
|
||||
// allocation can throw regardless of whether `value_type`'s move constructor
|
||||
// is specified as `noexcept`.
|
||||
InlinedVector(InlinedVector&& v, const allocator_type& alloc) noexcept(
|
||||
absl::allocator_is_nothrow<allocator_type>::value);
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue