From 0fc039df1e287b5c5493484966fe0cb03d259404 Mon Sep 17 00:00:00 2001 From: Marshall Clow Date: Tue, 6 Feb 2018 01:59:28 +0000 Subject: [PATCH] More patches ready llvm-svn: 324307 --- libcxx/www/upcoming_meeting.html | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/libcxx/www/upcoming_meeting.html b/libcxx/www/upcoming_meeting.html index 92053bec81dc..fadd4e8beff1 100644 --- a/libcxx/www/upcoming_meeting.html +++ b/libcxx/www/upcoming_meeting.html @@ -63,8 +63,8 @@ 2243istream::putback problemJacksonvilleComplete 2816resize_file has impossible postconditionJacksonvilleNothing to do 2843Unclear behavior of std::pmr::memory_resource::do_allocate()Jacksonville -2849Why does !is_regular_file(from) cause copy_file to report a "file already exists" error?JacksonvilleNothing to do -2851std::filesystem enum classes are now underspecifiedJacksonvilleNothing to do +2849Why does !is_regular_file(from) cause copy_file to report a "file already exists" error?JacksonvilleNothing to do +2851std::filesystem enum classes are now underspecifiedJacksonvilleNothing to do 2969polymorphic_allocator::construct() shouldn't pass resource()Jacksonville 2975Missing case for pair construction in scoped and polymorphic allocatorsJacksonville 2989path's stream insertion operator lets you insert everything under the sunJacksonvilleCompleted @@ -77,15 +77,15 @@ 3010[networking.ts] uses_executor says "if a type T::executor_type exists"Jacksonville 3013(recursive_)directory_iterator construction and traversal should not be noexceptJacksonvilleComplete 3014More noexcept issues with filesystem operationsJacksonvilleComplete - 3015copy_options::unspecified underspecifiedJacksonvilleNothing to do +3015copy_options::unspecified underspecifiedJacksonvilleNothing to do 3017list splice functions should use addressofJacksonville 3020[networking.ts] Remove spurious nested value_type buffer sequence requirementJacksonville 3026filesystem::weakly_canonical still defined in terms of canonical(p, base)Jacksonville 3030Who shall meet the requirements of try_lock?Jacksonville 3034P0767R1 breaks previously-standard-layout typesJacksonville -3035std::allocator's constructors should be constexprJacksonville -3039Unnecessary decay in thread and packaged_taskJacksonville -3041Unnecessary decay in reference_wrapperJacksonville +3035std::allocator's constructors should be constexprJacksonvillePatch Ready +3039Unnecessary decay in thread and packaged_taskJacksonvillePatch Ready +3041Unnecessary decay in reference_wrapperJacksonvillePatch Ready 3042is_literal_type_v should be inlineJacksonvilleComplete 3043Bogus postcondition for filesystem_error constructorJacksonville 3045atomic<floating-point> doesn't have value_type or difference_typeJacksonville @@ -131,7 +131,7 @@
  • 3026 - I think this is just wording cleanup - Eric?
  • 3030 - Wording changes only?? Do we handle exceptions correctly here?
  • 3034 - Need to check if our tests are correct.
    • -
  • 3035 - Easy to do
    • +
  • 3035 - Patch Ready
  • 3039 - Patch Ready
  • 3041 - Patch Ready
  • 3042 - We already do this.