tree 1af94aa103f8ea1bec1170dedee0099179990f55
parent d5549ccac174725e54d1be940a5404b70ced559a
author Marshall Clow <mclow.lists@gmail.com> 1405955473 +0000
committer Marshall Clow <mclow.lists@gmail.com> 1405955473 +0000

In response to bug #20362, change the order of operations in vector move assignment so that if the allocator move assignment throws, we aren't left with two objects pointing at the same memory. This is not a complete fix; I am unconvinced that a complete fix is possible. With this change in place, we will leak the old contents of the vector. LWG issue #2106, when adopted, will make this problem illegal. Thanks to Thomas Koeppe for the report and analysis.

git-svn-id: https://llvm.org/svn/llvm-project/libcxx/trunk@213546 91177308-0d34-0410-b5e6-96231b3b80d8