From 2a258956b0bb57164efd7f91f5e198d301e8c0eb Mon Sep 17 00:00:00 2001 From: Marshall Clow Date: Wed, 4 Sep 2013 00:18:19 +0000 Subject: [PATCH] Update status of issues 2045, 2050, 2080, 2081, 2083, 2130, 2137 and 2177. git-svn-id: https://llvm.org/svn/llvm-project/libcxx/trunk@189894 91177308-0d34-0410-b5e6-96231b3b80d8 --- www/cxx1y_status.html | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/www/cxx1y_status.html b/www/cxx1y_status.html index afd51eba4..ebd58b1cf 100644 --- a/www/cxx1y_status.html +++ b/www/cxx1y_status.html @@ -108,9 +108,9 @@ 2033Preconditions of reserve, shrink_to_fit, and resize functionsKonaComplete 2039Issues with std::reverse and std::copy_ifKonaComplete 2044No definition of "Stable" for copy algorithmsKonaComplete - 2045forward_list::merge and forward_list::splice_after with unequal allocatorsKona + 2045forward_list::merge and forward_list::splice_after with unequal allocatorsKonaComplete 2047Incorrect "mixed" move-assignment semantics of unique_ptrKonaComplete - 2050Unordered associative containers do not use allocator_traits to define member typesKona + 2050Unordered associative containers do not use allocator_traits to define member typesKonaComplete 2053Errors in regex bitmask typesKonaComplete 2061make_move_iterator and arraysKonaComplete 2064More noexcept issues in basic_stringKonaComplete @@ -122,7 +122,7 @@ 2071std::valarray move-assignmentPortlandComplete 2074Off by one error in std::reverse_copyPortlandComplete - 2081Allocator requirements should include CopyConstructible 2083 const-qualification on weak_ptr::owner_beforePortland + 2081Allocator requirements should include CopyConstructible 2083 const-qualification on weak_ptr::owner_beforePortlandComplete 2083const-qualification on weak_ptr::owner_beforePortlandComplete 2086Overly generic type support for math functionsPortland 2099Unnecessary constraints of va_start() usagePortlandComplete @@ -151,11 +151,11 @@ 2163nth_element requires inconsistent post-conditionsBristolComplete 2169Missing reset() requirements in unique_ptr specializationBristol 2172Does atomic_compare_exchange_* accept v == nullptr arguments?BristolComplete - 2080Specify when once_flag becomes invalidBristol + 2080Specify when once_flag becomes invalidBristolComplete 2098promise throws clausesBristolComplete 2109Incorrect requirements for hash specializationsBristolComplete - 2130missing ordering constraints for fencesBristol - 2138atomic_flag::clear ordering constraintsBristol + 2130missing ordering constraints for fencesBristolComplete + 2138atomic_flag::clear ordering constraintsBristolComplete 2140notify_all_at_thread_exit synchronizationBristol 2144Missing noexcept specification in type_indexBristolComplete 2174wstring_convert::converted() should be noexceptBristolComplete