absl::InlinedVector doesn't support move constructors which throw about abseil-cpp HOT 3 CLOSED

On a slightly pedantic note, an InlinedVector of objects in maybe-moved-from states is still in a valid state, so this technically satisfies basic exception safety -- but I agree it's not a nice thing to do.

I think this is a two step solution -- we declare that InlinedVector only supports T with nothrow move operators in the short term.

In the long term, Abseil's stance on throwing moves constructors is essentially that move constructors can only throw if the allocator can throw -- we're stricter than the standard on thsi point of view. So as I ramp up the exception-safety test suite we can advise the move constructor to be noexcept if the allocator is noexcept and use the current algorithm, and fall back to copying only if the allocator throws and T has a throwing move constructor.

Does this sound reasonable?

from abseil-cpp.

User reported test case at http://codepad.org/YbVsjMy5 but it seems to be inaccessible now.

from abseil-cpp.

Closing as a duplicate of #37

from abseil-cpp.