maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/libcxx/docs/Status/Cxx20Issues.csv

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

301 lines
38 KiB
Plaintext
Raw Normal View History

[libc++][doc] Use issue labels. During the review of D111166 I had a private discussion with @ldionne to avoid the duplication of the C++2b issues in the Ranges and Format status pages. The main reason for duplicating them is to make it easier to find them. The title of the paper may not always make it clear to which project the paper belongs. This commit removes all LWG-issues from the Ranges and Format status page and adds labels for these issue in the C++20/C++23 issues list. A quick scan revealed there are some issues that are missing a label since they weren't on the ranges issue list. These can be labelled in a separate commit. In that commit I'll also look for issues for the spaceship operator and chrono. Reviewed By: Quuxplusone, ldionne, #libc Differential Revision: https://reviews.llvm.org/D111458
2021-10-09 03:01:55 +08:00
"Issue #","Issue Name","Meeting","Status","First released version","Labels"
[libc++] [docs] Add Version column to issues tables on status pages.
2020-12-05 01:41:51 +08:00
"`2070 <https://wg21.link/LWG2070>`__","``allocate_shared``\ should use ``allocator_traits<A>::construct``\ ","Toronto","Resolved by `P0674R1 <https://wg21.link/P0674R1>`__",""
"`2444 <https://wg21.link/LWG2444>`__","Inconsistent complexity for ``std::sort_heap``\ ","Toronto","",""
"`2593 <https://wg21.link/LWG2593>`__","Moved-from state of Allocators","Toronto","",""
"`2597 <https://wg21.link/LWG2597>`__","``std::log``\ misspecified for complex numbers","Toronto","",""
"`2783 <https://wg21.link/LWG2783>`__","``stack::emplace()``\ and ``queue::emplace()``\ should return ``decltype(auto)``\ ","Toronto","|Complete|",""
"`2932 <https://wg21.link/LWG2932>`__","Constraints on parallel algorithm implementations are underspecified","Toronto","",""
"`2937 <https://wg21.link/LWG2937>`__","Is ``equivalent(""existing_thing"", ""not_existing_thing"")``\ an error","Toronto","|Complete|",""
"`2940 <https://wg21.link/LWG2940>`__","``result_of``\ specification also needs a little cleanup","Toronto","",""
"`2942 <https://wg21.link/LWG2942>`__","LWG 2873's resolution missed ``weak_ptr::owner_before``\ ","Toronto","|Complete|",""
"`2954 <https://wg21.link/LWG2954>`__","Specialization of the convenience variable templates should be prohibited","Toronto","|Complete|",""
"`2961 <https://wg21.link/LWG2961>`__","Bad postcondition for ``set_default_resource``\ ","Toronto","",""
"`2966 <https://wg21.link/LWG2966>`__","Incomplete resolution of US 74","Toronto","|Nothing To Do|",""
"`2974 <https://wg21.link/LWG2974>`__","Diagnose out of bounds ``tuple_element/variant_alternative``\ ","Toronto","|Complete|",""
"","","","",""
"`2779 <https://wg21.link/LWG2779>`__","[networking.ts] Relax requirements on buffer sequence iterators","Albuquerque","",""
"`2870 <https://wg21.link/LWG2870>`__","Default value of parameter theta of polar should be dependent","Albuquerque","|Complete|",""
[libc++] [P1164] [C++20] Make fs::create_directory() error if there is already a non-directory. Also mark LWG2935 and LWG3079 as complete. Applied retroactively to previous standards too, as it's a DR. * https://wg21.link/P1164 * https://wg21.link/lwg2935 * https://wg21.link/lwg3079 Reviewed By: ldionne, #libc Differential Revision: https://reviews.llvm.org/D92769
2020-12-10 15:38:41 +08:00
"`2935 <https://wg21.link/LWG2935>`__","What should create_directories do when p already exists but is not a directory?","Albuquerque","|Nothing To Do|",""
[libc++] [docs] Add Version column to issues tables on status pages.
2020-12-05 01:41:51 +08:00
"`2941 <https://wg21.link/LWG2941>`__","[thread.req.timing] wording should apply to both member and namespace-level functions","Albuquerque","|Nothing To Do|",""
"`2944 <https://wg21.link/LWG2944>`__","LWG 2905 accidentally removed requirement that construction of the deleter doesn't throw an exception","Albuquerque","|Nothing To Do|",""
"`2945 <https://wg21.link/LWG2945>`__","Order of template parameters in optional comparisons","Albuquerque","|Complete|",""
"`2948 <https://wg21.link/LWG2948>`__","unique_ptr does not define operator<< for stream output","Albuquerque","|Complete|",""
"`2950 <https://wg21.link/LWG2950>`__","std::byte operations are misspecified","Albuquerque","|Complete|",""
"`2952 <https://wg21.link/LWG2952>`__","iterator_traits should work for pointers to cv T","Albuquerque","|Complete|",""
"`2953 <https://wg21.link/LWG2953>`__","LWG 2853 should apply to deque::erase too","Albuquerque","|Complete|",""
[libc++][doc] Adds more issue status labels. A followup to D111458 adding more labels to LWG-issues. This should add the labels for the not completed chrono, format, ranges, and spaceship issues. Some minor formatting cleanups along the way. Reviewed By: #libc, Quuxplusone Differential Revision: https://reviews.llvm.org/D111935
2021-10-16 18:22:25 +08:00
"`2958 <https://wg21.link/LWG2958>`__","Moves improperly defined as deleted","Albuquerque","|Complete|",""
[libc++] [docs] Add Version column to issues tables on status pages.
2020-12-05 01:41:51 +08:00
"`2964 <https://wg21.link/LWG2964>`__","Apparently redundant requirement for dynamic_pointer_cast","Albuquerque","",""
"`2965 <https://wg21.link/LWG2965>`__","Non-existing path::native_string() in filesystem_error::what() specification","Albuquerque","|Nothing To Do|",""
"`2972 <https://wg21.link/LWG2972>`__","What is ``is_trivially_destructible_v<int>``\ ?","Albuquerque","|Complete|",""
"`2976 <https://wg21.link/LWG2976>`__","Dangling uses_allocator specialization for packaged_task","Albuquerque","|Complete|",""
"`2977 <https://wg21.link/LWG2977>`__","unordered_meow::merge() has incorrect Throws: clause","Albuquerque","|Nothing To Do|",""
"`2978 <https://wg21.link/LWG2978>`__","Hash support for pmr::string and friends","Albuquerque","",""
"`2979 <https://wg21.link/LWG2979>`__","aligned_union should require complete object types","Albuquerque","|Complete|",""
"`2980 <https://wg21.link/LWG2980>`__","Cannot compare_exchange empty pointers","Albuquerque","",""
[libc++] P0433R2: add the remaining deduction guides. Add deduction guides to `valarray` and `scoped_allocator_adaptor`. This largely finishes implementation of the paper: * deduction guides for other classes mentioned in the paper were implemented previously (see the list below); * deduction guides for several classes contained in the proposal (`reference_wrapper`, `lock_guard`, `scoped_lock`, `unique_lock`, `shared_lock`) were removed by [LWG2981](https://wg21.link/LWG2981). Also add deduction guides to the synopsis for the few classes (e.g. `pair`) where they were missing. The only part of the paper that isn't fully implemented after this patch is making sure certain deduction guides don't participate in overload resolution when given incorrect template parameters. List of significant commits implementing the other parts of P0433 (omitting some minor fixes): * [pair](https://github.com/llvm/llvm-project/commit/af65856eec160d163c764faad250d93357be7c83) * [basic_string](https://github.com/llvm/llvm-project/commit/6d9f750dec29e8ae5366092e64cd343dae2c7464) * [array](https://github.com/llvm/llvm-project/commit/0ca8c0895c6034615593c295dd955f29b25bf3d4) * [deque](https://github.com/llvm/llvm-project/commit/dbb6f8a8179b0604e25707b5c1b72be6164f62d9) * [forward_list](https://github.com/llvm/llvm-project/commit/e076700b7786959206acef136ecf05d54078e4e1) * [list](https://github.com/llvm/llvm-project/commit/4a227e582b2f13880ea049b29988a37a0f7c0742) * [vector](https://github.com/llvm/llvm-project/commit/df8f75479278d5ce16eede342ceb5ba2fd71460b) * [queue/stack/priority_queue](https://github.com/llvm/llvm-project/commit/5b8b8b5dce587f1e5a4a31cc24f09b18bd53ff9a) * [basic_regex](https://github.com/llvm/llvm-project/commit/edd5e29cfe9f67ec8e7e0eda12eb05e616fdeebc) * [optional](https://github.com/llvm/llvm-project/commit/f35b4bc3954f3b01051fc0848535ff784809e9e2) * [map/multimap](https://github.com/llvm/llvm-project/commit/edfe8525de1f7278f4754f2bffd47b13ec291a17) * [set/multiset](https://github.com/llvm/llvm-project/commit/e20865c387e09ea0ebd5add15c762cd5271ff65f) * [unordered_set/unordered_multiset](https://github.com/llvm/llvm-project/commit/296a80102a9b72c3eda80558fb78a3ed8849b341) * [unordered_map/unordered_multimap](https://github.com/llvm/llvm-project/commit/dfcd4384cbcac0eeb7e5cbce350f875ba4da79d5) * [function](https://github.com/llvm/llvm-project/commit/e1eabcdfad89f67ae575b0c86aa4a72d277378b4) * [tuple](https://github.com/llvm/llvm-project/commit/1308011e1b5c5382281a63dd4191a1784f8d2295) * [shared_ptr/weak_ptr](https://github.com/llvm/llvm-project/commit/83564056d4b186c9fcf016cdbb388755009f7b5a) Additional notes: * It was revision 2 of the paper that was voted into the Standard. P0433R3 is a separate paper that is not part of the Standard. * The paper also mandates removing several `make_*_searcher` functions (e.g. `make_boyer_moore_searcher`) which are currently not implemented (except in `experimental/`). * The `__cpp_lib_deduction_guides` feature test macro from the paper was accidentally omitted from the Standard. Differential Revision: https://reviews.llvm.org/D112510
2021-10-28 15:36:19 +08:00
"`2981 <https://wg21.link/LWG2981>`__","Remove redundant deduction guides from standard library","Albuquerque","|Nothing To Do|",""
[libc++] [docs] Add Version column to issues tables on status pages.
2020-12-05 01:41:51 +08:00
"`2982 <https://wg21.link/LWG2982>`__","Making size_type consistent in associative container deduction guides","Albuquerque","",""
[libc++] Update atomic synopsis and tests. While looking at LWG-2988 and P0558 it seems the issues were already implemented, but the synopsis wasn't updated. Some of the tests didn't validate the `noexcept` status. A few tests were missing completely: - `atomic_wait_explicit` - `atomic_notify_one` - `atomic_notify_all` Mark P0558 as complete, didn't investigate which version of libc++ first includes this. It seems the paper has been retroactively applied. I couldn't find whether this is correct, but looking at cppreference it seems intended. Completes - LWG-2988 Clause 32 cleanup missed one typename - P0558 Resolving atomic<T> named base class inconsistencies Reviewed By: #libc, ldionne Differential Revision: https://reviews.llvm.org/D103765
2021-06-06 20:48:08 +08:00
"`2988 <https://wg21.link/LWG2988>`__","Clause 32 cleanup missed one typename","Albuquerque","|Complete|","13.0"
[libc++] [LWG2993] reference_wrapper<T> conversion from U&& Implement the resolution of LWG2993. Replace a deleted constructor with a constructor that SFINAEs away in appropriate circumstances. Also, now that the constructor is templated, we must have an explicit deduction guide to make CTAD work. Some tests have been merged in from Agustín Bergé's D40259. Differential Revision: https://reviews.llvm.org/D92725
2020-12-06 08:37:41 +08:00
"`2993 <https://wg21.link/LWG2993>`__","reference_wrapper<T> conversion from T&&","Albuquerque","|Complete|","13.0"
[libc++] [docs] Add Version column to issues tables on status pages.
2020-12-05 01:41:51 +08:00
"`2998 <https://wg21.link/LWG2998>`__","Requirements on function objects passed to {``forward_``,}list-specific algorithms","Albuquerque","|Nothing To Do|",""
[libc++] LWG3001: add `remove_extent_t` to `weak_ptr::element_type`. Also fix a few places in the `shared_ptr` implementation where `element_type` was passed to the `__is_compatible` helper. This could result in `remove_extent` being applied twice to the pointer's template type (first by the definition of `element_type` and then by the helper), potentially leading to somewhat less readable error messages for some incorrect code. Differential Revision: https://reviews.llvm.org/D112092
2021-10-25 23:15:38 +08:00
"`3001 <https://wg21.link/LWG3001>`__","weak_ptr::element_type needs remove_extent_t","Albuquerque","|Complete|","14.0"
[libc++] [docs] Add Version column to issues tables on status pages.
2020-12-05 01:41:51 +08:00
"`3024 <https://wg21.link/LWG3024>`__","variant's copies must be deleted instead of disabled via SFINAE","Albuquerque","|Complete|",""
"","","","",""
"`2164 <https://wg21.link/LWG2164>`__","What are the semantics of ``vector.emplace(vector.begin(), vector.back())``\ ?","Jacksonville","|Complete|",""
"`2243 <https://wg21.link/LWG2243>`__","``istream::putback``\ problem","Jacksonville","|Complete|",""
"`2816 <https://wg21.link/LWG2816>`__","``resize_file``\ has impossible postcondition","Jacksonville","|Nothing To Do|",""
"`2843 <https://wg21.link/LWG2843>`__","Unclear behavior of ``std::pmr::memory_resource::do_allocate()``\ ","Jacksonville","|Complete|",""
"`2849 <https://wg21.link/LWG2849>`__","Why does ``!is_regular_file(from)``\ cause ``copy_file``\ to report a ""file already exists"" error?","Jacksonville","|Nothing To Do|",""
"`2851 <https://wg21.link/LWG2851>`__","``std::filesystem``\ enum classes are now underspecified","Jacksonville","|Nothing To Do|",""
"`2946 <https://wg21.link/LWG2946>`__","LWG 2758's resolution missed further corrections","Jacksonville","|Complete|",""
"`2969 <https://wg21.link/LWG2969>`__","``polymorphic_allocator::construct()``\ shouldn't pass ``resource()``\ ","Jacksonville","|Complete|",""
"`2975 <https://wg21.link/LWG2975>`__","Missing case for ``pair``\ construction in scoped and polymorphic allocators","Jacksonville","",""
"`2989 <https://wg21.link/LWG2989>`__","``path``\ 's stream insertion operator lets you insert everything under the sun","Jacksonville","|Complete|",""
"`3000 <https://wg21.link/LWG3000>`__","``monotonic_memory_resource::do_is_equal``\ uses ``dynamic_cast``\ unnecessarily","Jacksonville","",""
"`3002 <https://wg21.link/LWG3002>`__","[networking.ts] ``basic_socket_acceptor::is_open()``\ isn't ``noexcept``\ ","Jacksonville","",""
"`3004 <https://wg21.link/LWG3004>`__","|sect|\ [string.capacity] and |sect|\ [vector.capacity] should specify time complexity for ``capacity()``\ ","Jacksonville","|Nothing To Do|",""
"`3005 <https://wg21.link/LWG3005>`__","Destruction order of arrays by ``make_shared/allocate_shared``\ only recommended?","Jacksonville","",""
"`3007 <https://wg21.link/LWG3007>`__","``allocate_shared``\ should rebind allocator to *cv*-unqualified ``value_type``\ for construction","Jacksonville","",""
"`3009 <https://wg21.link/LWG3009>`__","Including ``<string_view>``\ doesn't provide ``std::size/empty/data``\ ","Jacksonville","|Complete|",""
"`3010 <https://wg21.link/LWG3010>`__","[networking.ts] ``uses_executor``\ says ""if a type ``T::executor_type``\ exists""","Jacksonville","",""
"`3013 <https://wg21.link/LWG3013>`__","``(recursive_)directory_iterator``\ construction and traversal should not be ``noexcept``\ ","Jacksonville","|Complete|",""
"`3014 <https://wg21.link/LWG3014>`__","More ``noexcept``\ issues with filesystem operations","Jacksonville","|Complete|",""
"`3015 <https://wg21.link/LWG3015>`__","``copy_options::*unspecified*``\ underspecified","Jacksonville","|Nothing To Do|",""
"`3017 <https://wg21.link/LWG3017>`__","``list splice``\ functions should use ``addressof``\ ","Jacksonville","|Complete|",""
"`3020 <https://wg21.link/LWG3020>`__","[networking.ts] Remove spurious nested ``value_type``\ buffer sequence requirement","Jacksonville","",""
"`3026 <https://wg21.link/LWG3026>`__","``filesystem::weakly_canonical``\ still defined in terms of ``canonical(p, base)``\ ","Jacksonville","|Complete|",""
"`3030 <https://wg21.link/LWG3030>`__","Who shall meet the requirements of ``try_lock``\ ?","Jacksonville","|Nothing To Do|",""
"`3034 <https://wg21.link/LWG3034>`__","P0767R1 breaks previously-standard-layout types","Jacksonville","|Complete|",""
"`3035 <https://wg21.link/LWG3035>`__","``std::allocator``\ 's constructors should be ``constexpr``\ ","Jacksonville","|Complete|",""
"`3039 <https://wg21.link/LWG3039>`__","Unnecessary ``decay``\ in ``thread``\ and ``packaged_task``\ ","Jacksonville","|Complete|",""
"`3041 <https://wg21.link/LWG3041>`__","Unnecessary ``decay``\ in ``reference_wrapper``\ ","Jacksonville","|Complete|",""
"`3042 <https://wg21.link/LWG3042>`__","``is_literal_type_v``\ should be inline","Jacksonville","|Complete|",""
"`3043 <https://wg21.link/LWG3043>`__","Bogus postcondition for ``filesystem_error``\ constructor","Jacksonville","|Complete|",""
[libc++][doc] Adds more issue status labels. A followup to D111458 adding more labels to LWG-issues. This should add the labels for the not completed chrono, format, ranges, and spaceship issues. Some minor formatting cleanups along the way. Reviewed By: #libc, Quuxplusone Differential Revision: https://reviews.llvm.org/D111935
2021-10-16 18:22:25 +08:00
"`3045 <https://wg21.link/LWG3045>`__","``atomic<floating-point>``\ doesn't have ``value_type``\ or ``difference_type``\ ","Jacksonville","",""
[libc++] [docs] Add Version column to issues tables on status pages.
2020-12-05 01:41:51 +08:00
"`3048 <https://wg21.link/LWG3048>`__","``transform_reduce(exec, first1, last1, first2, init)``\ discards execution policy","Jacksonville","",""
"`3051 <https://wg21.link/LWG3051>`__","Floating point classifications were inadvertently changed in P0175","Jacksonville","|Nothing To Do|",""
"`3075 <https://wg21.link/LWG3075>`__","``basic_string``\ needs deduction guides from ``basic_string_view``\ ","Jacksonville","|Complete|",""
"","","","",""
"`2139 <https://wg21.link/LWG2139>`__","What is a user-defined type?","Rapperswil","",""
"`2970 <https://wg21.link/LWG2970>`__","Return type of std::visit misspecified","Rapperswil","",""
"`3058 <https://wg21.link/LWG3058>`__","Parallel adjacent_difference shouldn't require creating temporaries","Rapperswil","",""
"`3062 <https://wg21.link/LWG3062>`__","Unnecessary decay_t in is_execution_policy_v should be remove_cvref_t","Rapperswil","",""
"`3067 <https://wg21.link/LWG3067>`__","recursive_directory_iterator::pop must invalidate","Rapperswil","|Nothing To Do|",""
"`3071 <https://wg21.link/LWG3071>`__","[networking.ts] read_until still refers to ""input sequence""","Rapperswil","|Nothing To Do|",""
"`3074 <https://wg21.link/LWG3074>`__","Non-member functions for valarray should only deduce from the valarray","Rapperswil","",""
"`3076 <https://wg21.link/LWG3076>`__","basic_string CTAD ambiguity","Rapperswil","|Complete|",""
[libc++] [P1164] [C++20] Make fs::create_directory() error if there is already a non-directory. Also mark LWG2935 and LWG3079 as complete. Applied retroactively to previous standards too, as it's a DR. * https://wg21.link/P1164 * https://wg21.link/lwg2935 * https://wg21.link/lwg3079 Reviewed By: ldionne, #libc Differential Revision: https://reviews.llvm.org/D92769
2020-12-10 15:38:41 +08:00
"`3079 <https://wg21.link/LWG3079>`__","LWG 2935 forgot to fix the existing_p overloads of create_directory","Rapperswil","|Nothing To Do|",""
[libc++] [docs] Add Version column to issues tables on status pages.
2020-12-05 01:41:51 +08:00
"`3080 <https://wg21.link/LWG3080>`__","Floating point from_chars pattern specification breaks round-tripping","Rapperswil","",""
"`3083 <https://wg21.link/LWG3083>`__","What should ios::iword(-1) do?","Rapperswil","|Nothing To Do|",""
"`3094 <https://wg21.link/LWG3094>`__","[time.duration.io]p4 makes surprising claims about encoding","Rapperswil","",""
"`3100 <https://wg21.link/LWG3100>`__","Unnecessary and confusing ""empty span"" wording","Rapperswil","|Nothing To Do|",""
"`3102 <https://wg21.link/LWG3102>`__","Clarify span iterator and ``const_iterator`` behavior","Rapperswil","|Complete|",""
"`3104 <https://wg21.link/LWG3104>`__","Fixing duration division","Rapperswil","|Complete|",""
"","","","",""
"`2183 <https://wg21.link/LWG2183>`__","Muddled allocator requirements for ``match_results``\ constructors","San Diego","|Complete|",""
"`2184 <https://wg21.link/LWG2184>`__","Muddled allocator requirements for ``match_results``\ assignments","San Diego","|Complete|",""
"`2412 <https://wg21.link/LWG2412>`__","``promise::set_value()``\ and ``promise::get_future()``\ should not race","San Diego","",""
"`2499 <https://wg21.link/LWG2499>`__","``operator>>(basic_istream&, CharT*)``\ makes it hard to avoid buffer overflows","San Diego","Resolved by P0487R1",""
"`2682 <https://wg21.link/LWG2682>`__","``filesystem::copy()``\ won't create a symlink to a directory","San Diego","|Nothing To Do|",""
"`2697 <https://wg21.link/LWG2697>`__","[concurr.ts] Behavior of ``future/shared_future``\ unwrapping constructor when given an invalid ``future``\ ","San Diego","",""
"`2797 <https://wg21.link/LWG2797>`__","Trait precondition violations","San Diego","Resolved by 1285R0",""
"`2936 <https://wg21.link/LWG2936>`__","Path comparison is defined in terms of the generic format","San Diego","|Complete|",""
"`2943 <https://wg21.link/LWG2943>`__","Problematic specification of the wide version of ``basic_filebuf::open``\ ","San Diego","|Nothing To Do|",""
"`2960 <https://wg21.link/LWG2960>`__","[fund.ts.v3] ``nonesuch``\ is insufficiently useless","San Diego","|Complete|",""
"`2995 <https://wg21.link/LWG2995>`__","``basic_stringbuf``\ default constructor forbids it from using SSO capacity","San Diego","",""
"`2996 <https://wg21.link/LWG2996>`__","Missing rvalue overloads for ``shared_ptr``\ operations","San Diego","",""
"`3008 <https://wg21.link/LWG3008>`__","``make_shared``\ (sub)object destruction semantics are not specified","San Diego","",""
"`3022 <https://wg21.link/LWG3022>`__","``is_convertible<derived*, base*>``\ may lead to ODR","San Diego","Resolved by 1285R0",""
"`3025 <https://wg21.link/LWG3025>`__","Map-like container deduction guides should use ``pair<Key, T>``\ , not ``pair<const Key, T>``\ ","San Diego","|Complete|",""
"`3031 <https://wg21.link/LWG3031>`__","Algorithms and predicates with non-const reference arguments","San Diego","",""
"`3037 <https://wg21.link/LWG3037>`__","``polymorphic_allocator``\ and incomplete types","San Diego","",""
[libcxx] Make allocator<T>:allocate throw bad_array_new_length Currently the member functions std::allocator<T>::allocate, std::experimental::pmr::polymorphic_allocator::allocate and std::resource_adaptor<T>::do_allocate throw an exception of type std::length_error when the requested size exceeds the maximum size. According to the C++ standard ([allocator.members]/4, [mem.poly.allocator.mem]/1), std::allocator<T>::allocate and std::pmr::polymorphic_allocator::allocate must throw a std::bad_array_new_length exception in this case. The patch fixes the issue with std::allocator<T>::allocate and changes the type the exception thrown by std::experimental::pmr::resource_adaptor<T>::do_allocate to std::bad_array_new_length as well for consistency. The patch resolves LWG 3237, LWG 3038 and LWG 3190. Reviewed By: ldionne, #libc, Quuxplusone Differential Revision: https://reviews.llvm.org/D110846
2021-10-19 02:12:42 +08:00
"`3038 <https://wg21.link/LWG3038>`__","``polymorphic_allocator::allocate``\ should not allow integer overflow to create vulnerabilities","San Diego","|Complete|","14.0"
[libc++] [docs] Add Version column to issues tables on status pages.
2020-12-05 01:41:51 +08:00
"`3054 <https://wg21.link/LWG3054>`__","``uninitialized_copy``\ appears to not be able to meet its exception-safety guarantee","San Diego","",""
"`3065 <https://wg21.link/LWG3065>`__","LWG 2989 missed that all ``path``\ 's other operators should be hidden friends as well","San Diego","|Complete|",""
"`3096 <https://wg21.link/LWG3096>`__","``path::lexically_relative``\ is confused by trailing slashes","San Diego","|Complete|",""
[libc++][doc] Adds more issue status labels. A followup to D111458 adding more labels to LWG-issues. This should add the labels for the not completed chrono, format, ranges, and spaceship issues. Some minor formatting cleanups along the way. Reviewed By: #libc, Quuxplusone Differential Revision: https://reviews.llvm.org/D111935
2021-10-16 18:22:25 +08:00
"`3116 <https://wg21.link/LWG3116>`__","``OUTERMOST_ALLOC_TRAITS``\ needs ``remove_reference_t``\ ","San Diego","",""
[libc++] [docs] Add Version column to issues tables on status pages.
2020-12-05 01:41:51 +08:00
"`3122 <https://wg21.link/LWG3122>`__","``__cpp_lib_chrono_udls``\ was accidentally dropped","San Diego","|Complete|",""
[libc++][doc] Adds more issue status labels. A followup to D111458 adding more labels to LWG-issues. This should add the labels for the not completed chrono, format, ranges, and spaceship issues. Some minor formatting cleanups along the way. Reviewed By: #libc, Quuxplusone Differential Revision: https://reviews.llvm.org/D111935
2021-10-16 18:22:25 +08:00
"`3127 <https://wg21.link/LWG3127>`__","``basic_osyncstream::rdbuf``\ needs a ``const_cast``\ ","San Diego","",""
"`3128 <https://wg21.link/LWG3128>`__","``strstream::rdbuf``\ needs a ``const_cast``\ ","San Diego","|Nothing To Do|",""
[libc++] [docs] Add Version column to issues tables on status pages.
2020-12-05 01:41:51 +08:00
"`3129 <https://wg21.link/LWG3129>`__","``regex_token_iterator``\ constructor uses wrong pointer arithmetic","San Diego","",""
"`3130 <https://wg21.link/LWG3130>`__","|sect|\ [input.output] needs many ``addressof``\ ","San Diego","",""
"`3131 <https://wg21.link/LWG3131>`__","``addressof``\ all the things","San Diego","",""
"`3132 <https://wg21.link/LWG3132>`__","Library needs to ban macros named ``expects``\ or ``ensures``\ ","San Diego","|Nothing To Do|",""
"`3134 <https://wg21.link/LWG3134>`__","[fund.ts.v3] LFTSv3 contains extraneous [meta] variable templates that should have been deleted by P09961","San Diego","Resolved by P1210R0",""
"`3137 <https://wg21.link/LWG3137>`__","Header for ``__cpp_lib_to_chars``\ ","San Diego","|Complete|",""
"`3145 <https://wg21.link/LWG3145>`__","``file_clock``\ breaks ABI for C++17 implementations","San Diego","|Complete|",""
"`3147 <https://wg21.link/LWG3147>`__","Definitions of ""likely"" and ""unlikely"" are likely to cause problems","San Diego","",""
"`3148 <https://wg21.link/LWG3148>`__","``<concepts>``\ should be freestanding","San Diego","",""
[libcxx][docs] Mark LWG3153 as complete Reviewed By: ldionne, #libc Differential Revision: https://reviews.llvm.org/D108967
2021-09-01 01:41:47 +08:00
"`3153 <https://wg21.link/LWG3153>`__","``Common``\ and ``common_type``\ have too little in common","San Diego","|Complete|","13.0"
[libc++] [docs] Add Version column to issues tables on status pages.
2020-12-05 01:41:51 +08:00
"`3154 <https://wg21.link/LWG3154>`__","``Common``\ and ``CommonReference``\ have a common defect","San Diego","",""
"","","","",""
"`3012 <https://wg21.link/LWG3012>`__","``atomic<T>``\ is unimplementable for non-``is_trivially_copy_constructible T``\ ","Kona","",""
"`3040 <https://wg21.link/LWG3040>`__","``basic_string_view::starts_with``\ *Effects* are incorrect","Kona","|Complete|",""
"`3077 <https://wg21.link/LWG3077>`__","``(push|emplace)_back``\ should invalidate the ``end``\ iterator","Kona","|Nothing To Do|",""
"`3087 <https://wg21.link/LWG3087>`__","One final ``&x``\ in |sect|\ [list.ops]","Kona","|Nothing To Do|",""
"`3101 <https://wg21.link/LWG3101>`__","``span``\ 's ``Container``\ constructors need another constraint","Kona","|Complete|",""
"`3112 <https://wg21.link/LWG3112>`__","``system_error``\ and ``filesystem_error``\ constructors taking a ``string``\ may not be able to meet their postconditions","Kona","",""
"`3119 <https://wg21.link/LWG3119>`__","Program-definedness of closure types","Kona","|Nothing To Do|",""
"`3133 <https://wg21.link/LWG3133>`__","Modernizing numeric type requirements","Kona","",""
[libc++][doc] Adds more issue status labels. A followup to D111458 adding more labels to LWG-issues. This should add the labels for the not completed chrono, format, ranges, and spaceship issues. Some minor formatting cleanups along the way. Reviewed By: #libc, Quuxplusone Differential Revision: https://reviews.llvm.org/D111935
2021-10-16 18:22:25 +08:00
"`3144 <https://wg21.link/LWG3144>`__","``span``\ does not have a ``const_pointer``\ typedef","Kona","|Complete|",""
"`3173 <https://wg21.link/LWG3173>`__","Enable CTAD for ``ref-view``\ ","Kona","","","|ranges|"
[libc++][doc] Use issue labels. During the review of D111166 I had a private discussion with @ldionne to avoid the duplication of the C++2b issues in the Ranges and Format status pages. The main reason for duplicating them is to make it easier to find them. The title of the paper may not always make it clear to which project the paper belongs. This commit removes all LWG-issues from the Ranges and Format status page and adds labels for these issue in the C++20/C++23 issues list. A quick scan revealed there are some issues that are missing a label since they weren't on the ranges issue list. These can be labelled in a separate commit. In that commit I'll also look for issues for the spaceship operator and chrono. Reviewed By: Quuxplusone, ldionne, #libc Differential Revision: https://reviews.llvm.org/D111458
2021-10-09 03:01:55 +08:00
"`3179 <https://wg21.link/LWG3179>`__","``subrange``\ should always model ``Range``\ ","Kona","","","|ranges|"
"`3180 <https://wg21.link/LWG3180>`__","Inconsistently named return type for ``ranges::minmax_element``\ ","Kona","","","|ranges|"
[libc++] [docs] Add Version column to issues tables on status pages.
2020-12-05 01:41:51 +08:00
"`3182 <https://wg21.link/LWG3182>`__","Specification of ``Same``\ could be clearer","Kona","",""
"","","","",""
"`2899 <https://wg21.link/LWG2899>`__","``is_(nothrow_)move_constructible``\ and ``tuple``\ , ``optional``\ and ``unique_ptr``\ ","Cologne","",""
[libc++] [docs] Mark LWG3055 as complete. Use string_view instead of string in path::operator+=(ECharT). The issue didn't change the behaviour which is tested in libcxx/test/std/input.output/filesystems/class.path/path.member/path.concat.pass.cpp. The change to use string_view instead of string is not strictly necessary. <filesystem> was added in commit 998a5c88312066fcc2b2de1358edc76587611354 (Implement <filesystem>). Reviewed By: #libc, ldionne Differential Revision: https://reviews.llvm.org/D92731
2020-12-08 03:07:25 +08:00
"`3055 <https://wg21.link/LWG3055>`__","``path::operator+=(*single-character*)``\ misspecified","Cologne","|Complete|","7.0"
[libc++][NFC] Mark LWG3158 as implemented It has been implemented in 59e26308e60a.
2021-09-25 02:10:19 +08:00
"`3158 <https://wg21.link/LWG3158>`__","``tuple(allocator_arg_t, const Alloc&)``\ should be conditionally explicit","Cologne","|Complete|","10.0"
[libc++][doc] Use issue labels. During the review of D111166 I had a private discussion with @ldionne to avoid the duplication of the C++2b issues in the Ranges and Format status pages. The main reason for duplicating them is to make it easier to find them. The title of the paper may not always make it clear to which project the paper belongs. This commit removes all LWG-issues from the Ranges and Format status page and adds labels for these issue in the C++20/C++23 issues list. A quick scan revealed there are some issues that are missing a label since they weren't on the ranges issue list. These can be labelled in a separate commit. In that commit I'll also look for issues for the spaceship operator and chrono. Reviewed By: Quuxplusone, ldionne, #libc Differential Revision: https://reviews.llvm.org/D111458
2021-10-09 03:01:55 +08:00
"`3169 <https://wg21.link/LWG3169>`__","``ranges``\ permutation generators discard useful information","Cologne","","","|ranges|"
"`3183 <https://wg21.link/LWG3183>`__","Normative permission to specialize Ranges variable templates","Cologne","","","|ranges|"
[libc++] Add bind_front function (P0356R5). Implementes [[ http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2018/p0356r5.html | P0356R5 ]]. Adds `bind_front` to `functional`. Reviewed By: ldionne, #libc, Quuxplusone Differential Revision: https://reviews.llvm.org/D60368
2021-03-03 08:17:22 +08:00
"`3184 <https://wg21.link/LWG3184>`__","Inconsistencies in ``bind_front``\ wording","Cologne","|Complete|","13.0"
[libc++] [docs] Add Version column to issues tables on status pages.
2020-12-05 01:41:51 +08:00
"`3185 <https://wg21.link/LWG3185>`__","Uses-allocator construction functions missing ``constexpr``\ and ``noexcept``\ ","Cologne","",""
[libc++][doc] Use issue labels. During the review of D111166 I had a private discussion with @ldionne to avoid the duplication of the C++2b issues in the Ranges and Format status pages. The main reason for duplicating them is to make it easier to find them. The title of the paper may not always make it clear to which project the paper belongs. This commit removes all LWG-issues from the Ranges and Format status page and adds labels for these issue in the C++20/C++23 issues list. A quick scan revealed there are some issues that are missing a label since they weren't on the ranges issue list. These can be labelled in a separate commit. In that commit I'll also look for issues for the spaceship operator and chrono. Reviewed By: Quuxplusone, ldionne, #libc Differential Revision: https://reviews.llvm.org/D111458
2021-10-09 03:01:55 +08:00
"`3186 <https://wg21.link/LWG3186>`__","``ranges``\ removal, partition, and ``partial_sort_copy``\ algorithms discard useful information","Cologne","","","|ranges|"
[libc++] [docs] Add Version column to issues tables on status pages.
2020-12-05 01:41:51 +08:00
"`3187 <https://wg21.link/LWG3187>`__","`P0591R4 <https://wg21.link/p0591r4>`__ reverted DR 2586 fixes to ``scoped_allocator_adaptor::construct()``\ ","Cologne","",""
[libc++][doc] Use issue labels. During the review of D111166 I had a private discussion with @ldionne to avoid the duplication of the C++2b issues in the Ranges and Format status pages. The main reason for duplicating them is to make it easier to find them. The title of the paper may not always make it clear to which project the paper belongs. This commit removes all LWG-issues from the Ranges and Format status page and adds labels for these issue in the C++20/C++23 issues list. A quick scan revealed there are some issues that are missing a label since they weren't on the ranges issue list. These can be labelled in a separate commit. In that commit I'll also look for issues for the spaceship operator and chrono. Reviewed By: Quuxplusone, ldionne, #libc Differential Revision: https://reviews.llvm.org/D111458
2021-10-09 03:01:55 +08:00
"`3191 <https://wg21.link/LWG3191>`__","``std::ranges::shuffle``\ synopsis does not match algorithm definition","Cologne","","","|ranges|"
[libc++] [docs] Add Version column to issues tables on status pages.
2020-12-05 01:41:51 +08:00
"`3196 <https://wg21.link/LWG3196>`__","``std::optional<T>``\ is ill-formed is ``T``\ is an array","Cologne","|Complete|",""
"`3198 <https://wg21.link/LWG3198>`__","Bad constraint on ``std::span::span()``\ ","Cologne","|Complete|",""
"`3199 <https://wg21.link/LWG3199>`__","``istream >> bitset<0>``\ fails","Cologne","",""
"`3202 <https://wg21.link/LWG3202>`__","P0318R1 was supposed to be revised","Cologne","|Complete|",""
"`3206 <https://wg21.link/LWG3206>`__","``year_month_day``\ conversion to ``sys_days``\ uses not-existing member function","Cologne","|Complete|",""
"`3208 <https://wg21.link/LWG3208>`__","``Boolean``\ 's expression requirements are ordered inconsistently","Cologne","|Nothing To Do|",""
"`3209 <https://wg21.link/LWG3209>`__","Expression in ``year::ok()``\ returns clause is ill-formed","Cologne","|Complete|",""
"","","","",""
"`3231 <https://wg21.link/LWG3231>`__","``year_month_day_last::day``\ specification does not cover ``!ok()``\ values","Belfast","|Nothing To Do|",""
[libc++][doc] Adds more issue status labels. A followup to D111458 adding more labels to LWG-issues. This should add the labels for the not completed chrono, format, ranges, and spaceship issues. Some minor formatting cleanups along the way. Reviewed By: #libc, Quuxplusone Differential Revision: https://reviews.llvm.org/D111935
2021-10-16 18:22:25 +08:00
"`3225 <https://wg21.link/LWG3225>`__","``zoned_time``\ converting constructor shall not be ``noexcept``\ ","Belfast","","","|chrono|"
[libcxx] Make allocator<T>:allocate throw bad_array_new_length Currently the member functions std::allocator<T>::allocate, std::experimental::pmr::polymorphic_allocator::allocate and std::resource_adaptor<T>::do_allocate throw an exception of type std::length_error when the requested size exceeds the maximum size. According to the C++ standard ([allocator.members]/4, [mem.poly.allocator.mem]/1), std::allocator<T>::allocate and std::pmr::polymorphic_allocator::allocate must throw a std::bad_array_new_length exception in this case. The patch fixes the issue with std::allocator<T>::allocate and changes the type the exception thrown by std::experimental::pmr::resource_adaptor<T>::do_allocate to std::bad_array_new_length as well for consistency. The patch resolves LWG 3237, LWG 3038 and LWG 3190. Reviewed By: ldionne, #libc, Quuxplusone Differential Revision: https://reviews.llvm.org/D110846
2021-10-19 02:12:42 +08:00
"`3190 <https://wg21.link/LWG3190>`__","``std::allocator::allocate``\ sometimes returns too little storage","Belfast","|Complete|","14.0"
[libc++][doc] Use issue labels. During the review of D111166 I had a private discussion with @ldionne to avoid the duplication of the C++2b issues in the Ranges and Format status pages. The main reason for duplicating them is to make it easier to find them. The title of the paper may not always make it clear to which project the paper belongs. This commit removes all LWG-issues from the Ranges and Format status page and adds labels for these issue in the C++20/C++23 issues list. A quick scan revealed there are some issues that are missing a label since they weren't on the ranges issue list. These can be labelled in a separate commit. In that commit I'll also look for issues for the spaceship operator and chrono. Reviewed By: Quuxplusone, ldionne, #libc Differential Revision: https://reviews.llvm.org/D111458
2021-10-09 03:01:55 +08:00
"`3218 <https://wg21.link/LWG3218>`__","Modifier for ``%d``\ parse flag does not match POSIX and ``format``\ specification","Belfast","","","|chrono| |format|"
[libc++][doc] Adds more issue status labels. A followup to D111458 adding more labels to LWG-issues. This should add the labels for the not completed chrono, format, ranges, and spaceship issues. Some minor formatting cleanups along the way. Reviewed By: #libc, Quuxplusone Differential Revision: https://reviews.llvm.org/D111935
2021-10-16 18:22:25 +08:00
"`3224 <https://wg21.link/LWG3224>`__","``zoned_time``\ constructor from ``TimeZonePtr``\ does not specify initialization of ``tp_``\ ","Belfast","","","|chrono|"
[libc++][doc] Use issue labels. During the review of D111166 I had a private discussion with @ldionne to avoid the duplication of the C++2b issues in the Ranges and Format status pages. The main reason for duplicating them is to make it easier to find them. The title of the paper may not always make it clear to which project the paper belongs. This commit removes all LWG-issues from the Ranges and Format status page and adds labels for these issue in the C++20/C++23 issues list. A quick scan revealed there are some issues that are missing a label since they weren't on the ranges issue list. These can be labelled in a separate commit. In that commit I'll also look for issues for the spaceship operator and chrono. Reviewed By: Quuxplusone, ldionne, #libc Differential Revision: https://reviews.llvm.org/D111458
2021-10-09 03:01:55 +08:00
"`3230 <https://wg21.link/LWG3230>`__","Format specifier ``%y/%Y``\ is missing locale alternative versions","Belfast","","","|chrono| |format|"
[libc++][doc] Adds more issue status labels. A followup to D111458 adding more labels to LWG-issues. This should add the labels for the not completed chrono, format, ranges, and spaceship issues. Some minor formatting cleanups along the way. Reviewed By: #libc, Quuxplusone Differential Revision: https://reviews.llvm.org/D111935
2021-10-16 18:22:25 +08:00
"`3232 <https://wg21.link/LWG3232>`__","Inconsistency in ``zoned_time``\ deduction guides","Belfast","","","|chrono|"
[libc++] [docs] Add Version column to issues tables on status pages.
2020-12-05 01:41:51 +08:00
"`3222 <https://wg21.link/LWG3222>`__","P0574R1 introduced preconditions on non-existent parameters","Belfast","",""
[libc++] [LWG3221] Add tests for wrapping operator+(year_month, months). The behaviour didn't change since commit 5b08c1742a536f54bd5e270b00ff851cbc7314ef (Recommit <chrono> changes with a couple xtra tests marked to fail on apple's clang.) * http://wg21.link/lwg3221 Reviewed By: ldionne, #libc Differential Revision: https://reviews.llvm.org/D92730
2020-12-09 01:07:25 +08:00
"`3221 <https://wg21.link/LWG3221>`__","Result of ``year_month``\ arithmetic with ``months``\ is ambiguous","Belfast","|Complete|","8.0"
[libc++] [docs] Add Version column to issues tables on status pages.
2020-12-05 01:41:51 +08:00
"`3235 <https://wg21.link/LWG3235>`__","``parse``\ manipulator without abbreviation is not callable","Belfast","",""
[libc++][doc] Use issue labels. During the review of D111166 I had a private discussion with @ldionne to avoid the duplication of the C++2b issues in the Ranges and Format status pages. The main reason for duplicating them is to make it easier to find them. The title of the paper may not always make it clear to which project the paper belongs. This commit removes all LWG-issues from the Ranges and Format status page and adds labels for these issue in the C++20/C++23 issues list. A quick scan revealed there are some issues that are missing a label since they weren't on the ranges issue list. These can be labelled in a separate commit. In that commit I'll also look for issues for the spaceship operator and chrono. Reviewed By: Quuxplusone, ldionne, #libc Differential Revision: https://reviews.llvm.org/D111458
2021-10-09 03:01:55 +08:00
"`3246 <https://wg21.link/LWG3246>`__","What are the constraints on the template parameter of ``basic_format_arg``\ ?","Belfast","","","|format|"
[libc++] [docs] Add Version column to issues tables on status pages.
2020-12-05 01:41:51 +08:00
"`3253 <https://wg21.link/LWG3253>`__","``basic_syncbuf::basic_syncbuf()``\ should not be explicit","Belfast","",""
[libc++][doc] Adds more issue status labels. A followup to D111458 adding more labels to LWG-issues. This should add the labels for the not completed chrono, format, ranges, and spaceship issues. Some minor formatting cleanups along the way. Reviewed By: #libc, Quuxplusone Differential Revision: https://reviews.llvm.org/D111935
2021-10-16 18:22:25 +08:00
"`3245 <https://wg21.link/LWG3245>`__","Unnecessary restriction on ``'%p'``\ parse specifier","Belfast","","","|chrono|"
[libc++] [docs] Add Version column to issues tables on status pages.
2020-12-05 01:41:51 +08:00
"`3244 <https://wg21.link/LWG3244>`__","Constraints for ``Source``\ in |sect|\ [fs.path.req] insufficiently constrainty","Belfast","",""
[libc++][doc] Use issue labels. During the review of D111166 I had a private discussion with @ldionne to avoid the duplication of the C++2b issues in the Ranges and Format status pages. The main reason for duplicating them is to make it easier to find them. The title of the paper may not always make it clear to which project the paper belongs. This commit removes all LWG-issues from the Ranges and Format status page and adds labels for these issue in the C++20/C++23 issues list. A quick scan revealed there are some issues that are missing a label since they weren't on the ranges issue list. These can be labelled in a separate commit. In that commit I'll also look for issues for the spaceship operator and chrono. Reviewed By: Quuxplusone, ldionne, #libc Differential Revision: https://reviews.llvm.org/D111458
2021-10-09 03:01:55 +08:00
"`3241 <https://wg21.link/LWG3241>`__","``chrono-spec``\ grammar ambiguity in |sect|\ [time.format]","Belfast","","","|chrono| |format|"
[libc++] [docs] Add Version column to issues tables on status pages.
2020-12-05 01:41:51 +08:00
"`3257 <https://wg21.link/LWG3257>`__","Missing feature testing macro update from P0858","Belfast","",""
[libc++] [P0879] constexpr std::sort This completes libc++'s implementation of P0879 "Constexpr for swap and swap related functions." http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2018/p0879r0.html For the feature-macro adjustment, see https://cplusplus.github.io/LWG/issue3256 Differential Revision: https://reviews.llvm.org/D93661
2020-12-21 04:21:42 +08:00
"`3256 <https://wg21.link/LWG3256>`__","Feature testing macro for ``constexpr``\ algorithms","Belfast","|Complete|","13.0"
[libc++][doc] Adds more issue status labels. A followup to D111458 adding more labels to LWG-issues. This should add the labels for the not completed chrono, format, ranges, and spaceship issues. Some minor formatting cleanups along the way. Reviewed By: #libc, Quuxplusone Differential Revision: https://reviews.llvm.org/D111935
2021-10-16 18:22:25 +08:00
"`3273 <https://wg21.link/LWG3273>`__","Specify ``weekday_indexed``\ to range of ``[0, 7]``\ ","Belfast","","","|chrono|"
[libc++] [docs] Add Version column to issues tables on status pages.
2020-12-05 01:41:51 +08:00
"`3070 <https://wg21.link/LWG3070>`__","``path::lexically_relative``\ causes surprising results if a filename can also be a *root-name*","Belfast","",""
[libc++] LWG3266: delete the to_chars(bool) overload. This PR only updates the synopsis in `<charconv>` -- the current implementation already [deletes](https://github.com/llvm/llvm-project/blob/e9e6266c704df43e2c52308e1b653dccefa89e04/libcxx/include/charconv#L108) the overload and has a [test](https://github.com/llvm/llvm-project/blob/main/libcxx/test/std/utilities/charconv/charconv.to.chars/integral.bool.fail.cpp) for it (and this has been the case from the first [commit](https://reviews.llvm.org/D41458) where `<charconv>` was added). Reviewed By: #libc, Mordante Differential Revision: https://reviews.llvm.org/D111845
2021-10-15 23:40:42 +08:00
"`3266 <https://wg21.link/LWG3266>`__","``to_chars(bool)``\ should be deleted","Belfast","|Complete|","14.0"
[libc++][doc] Use issue labels. During the review of D111166 I had a private discussion with @ldionne to avoid the duplication of the C++2b issues in the Ranges and Format status pages. The main reason for duplicating them is to make it easier to find them. The title of the paper may not always make it clear to which project the paper belongs. This commit removes all LWG-issues from the Ranges and Format status page and adds labels for these issue in the C++20/C++23 issues list. A quick scan revealed there are some issues that are missing a label since they weren't on the ranges issue list. These can be labelled in a separate commit. In that commit I'll also look for issues for the spaceship operator and chrono. Reviewed By: Quuxplusone, ldionne, #libc Differential Revision: https://reviews.llvm.org/D111458
2021-10-09 03:01:55 +08:00
"`3272 <https://wg21.link/LWG3272>`__","``%I%p``\ should parse/format ``duration``\ since midnight","Belfast","","","|chrono| |format|"
[libc++][doc] Adds more issue status labels. A followup to D111458 adding more labels to LWG-issues. This should add the labels for the not completed chrono, format, ranges, and spaceship issues. Some minor formatting cleanups along the way. Reviewed By: #libc, Quuxplusone Differential Revision: https://reviews.llvm.org/D111935
2021-10-16 18:22:25 +08:00
"`3259 <https://wg21.link/LWG3259>`__","The definition of *constexpr iterators* should be adjusted","Belfast","","","|ranges|"
[libc++] [docs] Add Version column to issues tables on status pages.
2020-12-05 01:41:51 +08:00
"`3103 <https://wg21.link/LWG3103>`__","Errors in taking subview of ``span``\ should be ill-formed where possible","Belfast","",""
[libc++][docs] Mark LWG3274 as complete Mark LWG3274 as complete. The feature test macro `__cpp_lib_span` was added in `6d2599e4f776d0cd88438cb82a00c4fc25cc3f67`. https://wg21.link/p1024 mentions marking `span:::empty()` with `[[nodiscard]]` which is not done yet. So, do that and add tests. Reviewed By: ldionne, Quuxplusone, Mordante, #libc Differential Revision: https://reviews.llvm.org/D111516
2021-10-13 10:30:58 +08:00
"`3274 <https://wg21.link/LWG3274>`__","Missing feature test macro for ``<span>``\ ","Belfast","|Complete|","11.0"
[libc++][doc] Use issue labels. During the review of D111166 I had a private discussion with @ldionne to avoid the duplication of the C++2b issues in the Ranges and Format status pages. The main reason for duplicating them is to make it easier to find them. The title of the paper may not always make it clear to which project the paper belongs. This commit removes all LWG-issues from the Ranges and Format status page and adds labels for these issue in the C++20/C++23 issues list. A quick scan revealed there are some issues that are missing a label since they weren't on the ranges issue list. These can be labelled in a separate commit. In that commit I'll also look for issues for the spaceship operator and chrono. Reviewed By: Quuxplusone, ldionne, #libc Differential Revision: https://reviews.llvm.org/D111458
2021-10-09 03:01:55 +08:00
"`3276 <https://wg21.link/LWG3276>`__","Class ``split_view::outer_iterator::value_type``\ should inherit from ``view_interface``\ ","Belfast","","","|ranges|"
[libc++][doc] Adds more issue status labels. A followup to D111458 adding more labels to LWG-issues. This should add the labels for the not completed chrono, format, ranges, and spaceship issues. Some minor formatting cleanups along the way. Reviewed By: #libc, Quuxplusone Differential Revision: https://reviews.llvm.org/D111935
2021-10-16 18:22:25 +08:00
"`3277 <https://wg21.link/LWG3277>`__","Pre-increment on prvalues is not a requirement of ``weakly_incrementable``\ ","Belfast","","","|ranges|"
[libc++] Implements concept default_initializable. Implements: - LWG3149 DefaultConstructible should require default initialization Implements parts of: - P0898R3 Standard Library Concepts - P1754 Rename concepts to standard_case for C++20, while we still can Depends on D91986 Reviewed By: ldionne, #libc Differential Revision: https://reviews.llvm.org/D93461
2020-12-17 14:48:26 +08:00
"`3149 <https://wg21.link/LWG3149>`__","``DefaultConstructible``\ should require default initialization","Belfast","|Complete|","13.0"
[libc++] [docs] Add Version column to issues tables on status pages.
2020-12-05 01:41:51 +08:00
"","","","",""
[NFC][libc++] Update C++20 issues status. Properly mark LWG1203 as completed and move the version number to the version column.
2020-12-05 23:36:19 +08:00
"`1203 <https://wg21.link/LWG1203>`__","More useful rvalue stream insertion","Prague","|Complete|","12.0"
[libc++] [docs] Add Version column to issues tables on status pages.
2020-12-05 01:41:51 +08:00
"`2859 <https://wg21.link/LWG2859>`__","Definition of *reachable* in [ptr.launder] misses pointer arithmetic from pointer-interconvertible object","Prague","",""
"`3018 <https://wg21.link/LWG3018>`__","``shared_ptr``\ of function type","Prague","",""
[libc++][doc] Adds more issue status labels. A followup to D111458 adding more labels to LWG-issues. This should add the labels for the not completed chrono, format, ranges, and spaceship issues. Some minor formatting cleanups along the way. Reviewed By: #libc, Quuxplusone Differential Revision: https://reviews.llvm.org/D111935
2021-10-16 18:22:25 +08:00
"`3050 <https://wg21.link/LWG3050>`__","Conversion specification problem in ``chrono::duration``\ constructor","Prague","","","|chrono|"
[libcxx] adds __cpp_lib_concepts feature-test macro Also adjusts C++20 status paper to indicate full concepts support. Depends on D96477, D99817. Differential Revision: https://reviews.llvm.org/D99805
2021-04-03 02:07:31 +08:00
"`3141 <https://wg21.link/LWG3141>`__","``CopyConstructible``\ doesn't preserve source values","Prague","|Nothing to do|",""
"`3150 <https://wg21.link/LWG3150>`__","``UniformRandomBitGenerator``\ should validate ``min``\ and ``max``\ ","Prague","|Complete|","13.0"
[libcxx] fixes `common_reference` requirement for `swappable_with` LWG3175 identifies that the `common_reference` requirement for `swappable_with` is over-constraining and doesn't need to concern itself with cv- or reference qualifiers. Differential Revision: https://reviews.llvm.org/D99817
2021-04-03 05:33:39 +08:00
"`3175 <https://wg21.link/LWG3175>`__","The ``CommonReference``\ requirement of concept ``SwappableWith``\ is not satisfied in the example","Prague","|Complete|","13.0"
[libcxx] adds __cpp_lib_concepts feature-test macro Also adjusts C++20 status paper to indicate full concepts support. Depends on D96477, D99817. Differential Revision: https://reviews.llvm.org/D99805
2021-04-03 02:07:31 +08:00
"`3194 <https://wg21.link/LWG3194>`__","``ConvertibleTo``\ prose does not match code","Prague","|Complete|","13.0"
[libc++] Mark LWG3200 as Nothing To Do. NFC. This is only a wording change, because it is currently impossible to constrain the overload set on whether the type is complete or not.
2020-12-08 16:00:45 +08:00
"`3200 <https://wg21.link/LWG3200>`__","``midpoint``\ should not constrain ``T``\ is complete","Prague","|Nothing To Do|",""
[libc++] [docs] Add Version column to issues tables on status pages.
2020-12-05 01:41:51 +08:00
"`3201 <https://wg21.link/LWG3201>`__","``lerp``\ should be marked as ``noexcept``\ ","Prague","|Complete|",""
[libc++][doc] Adds more issue status labels. A followup to D111458 adding more labels to LWG-issues. This should add the labels for the not completed chrono, format, ranges, and spaceship issues. Some minor formatting cleanups along the way. Reviewed By: #libc, Quuxplusone Differential Revision: https://reviews.llvm.org/D111935
2021-10-16 18:22:25 +08:00
"`3226 <https://wg21.link/LWG3226>`__","``zoned_time``\ constructor from ``string_view``\ should accept ``zoned_time<Duration2, TimeZonePtr2>``\ ","Prague","","","|chrono|"
[libc++] [docs] Add Version column to issues tables on status pages.
2020-12-05 01:41:51 +08:00
"`3233 <https://wg21.link/LWG3233>`__","Broken requirements for ``shared_ptr``\ converting constructors","Prague","",""
[libcxx] Make allocator<T>:allocate throw bad_array_new_length Currently the member functions std::allocator<T>::allocate, std::experimental::pmr::polymorphic_allocator::allocate and std::resource_adaptor<T>::do_allocate throw an exception of type std::length_error when the requested size exceeds the maximum size. According to the C++ standard ([allocator.members]/4, [mem.poly.allocator.mem]/1), std::allocator<T>::allocate and std::pmr::polymorphic_allocator::allocate must throw a std::bad_array_new_length exception in this case. The patch fixes the issue with std::allocator<T>::allocate and changes the type the exception thrown by std::experimental::pmr::resource_adaptor<T>::do_allocate to std::bad_array_new_length as well for consistency. The patch resolves LWG 3237, LWG 3038 and LWG 3190. Reviewed By: ldionne, #libc, Quuxplusone Differential Revision: https://reviews.llvm.org/D110846
2021-10-19 02:12:42 +08:00
"`3237 <https://wg21.link/LWG3237>`__","LWG 3038 and 3190 have inconsistent PRs","Prague","|Complete|","14.0"
[libc++] [docs] Add Version column to issues tables on status pages.
2020-12-05 01:41:51 +08:00
"`3238 <https://wg21.link/LWG3238>`__","Insufficiently-defined behavior of ``std::function``\ deduction guides","Prague","",""
[libc++][doc] Use issue labels. During the review of D111166 I had a private discussion with @ldionne to avoid the duplication of the C++2b issues in the Ranges and Format status pages. The main reason for duplicating them is to make it easier to find them. The title of the paper may not always make it clear to which project the paper belongs. This commit removes all LWG-issues from the Ranges and Format status page and adds labels for these issue in the C++20/C++23 issues list. A quick scan revealed there are some issues that are missing a label since they weren't on the ranges issue list. These can be labelled in a separate commit. In that commit I'll also look for issues for the spaceship operator and chrono. Reviewed By: Quuxplusone, ldionne, #libc Differential Revision: https://reviews.llvm.org/D111458
2021-10-09 03:01:55 +08:00
"`3242 <https://wg21.link/LWG3242>`__","``std::format``\ : missing rules for ``arg-id``\ in ``width``\ and ``precision``\ ","Prague","|Complete|","Clang 14","|format|"
[libc++][format] Adds formatter floating-point. This properly implements the formatter for floating-point types. Completes: - P1652R1 Printf corner cases in std::format - LWG 3250 std::format: # (alternate form) for NaN and inf - LWG 3243 std::format and negative zeroes Implements parts of: - P0645 Text Formatting Reviewed By: #libc, ldionne, vitaut Differential Revision: https://reviews.llvm.org/D114001
2020-12-15 00:39:15 +08:00
"`3243 <https://wg21.link/LWG3243>`__","``std::format``\ and negative zeroes","Prague","|Complete|","14.0","|format|"
[libc++][doc] Adds more issue status labels. A followup to D111458 adding more labels to LWG-issues. This should add the labels for the not completed chrono, format, ranges, and spaceship issues. Some minor formatting cleanups along the way. Reviewed By: #libc, Quuxplusone Differential Revision: https://reviews.llvm.org/D111935
2021-10-16 18:22:25 +08:00
"`3247 <https://wg21.link/LWG3247>`__","``ranges::iter_move``\ should perform ADL-only lookup of ``iter_move``\ ","Prague","","","|ranges|"
[libc++][doc] Use issue labels. During the review of D111166 I had a private discussion with @ldionne to avoid the duplication of the C++2b issues in the Ranges and Format status pages. The main reason for duplicating them is to make it easier to find them. The title of the paper may not always make it clear to which project the paper belongs. This commit removes all LWG-issues from the Ranges and Format status page and adds labels for these issue in the C++20/C++23 issues list. A quick scan revealed there are some issues that are missing a label since they weren't on the ranges issue list. These can be labelled in a separate commit. In that commit I'll also look for issues for the spaceship operator and chrono. Reviewed By: Quuxplusone, ldionne, #libc Differential Revision: https://reviews.llvm.org/D111458
2021-10-09 03:01:55 +08:00
"`3248 <https://wg21.link/LWG3248>`__","``std::format``\ ``#b``\ , ``#B``\ , ``#o``\ , ``#x``\ , and ``#X``\ presentation types misformat negative numbers","Prague","|Complete|","14.0","|format|"
[libc++][format] Adds formatter floating-point. This properly implements the formatter for floating-point types. Completes: - P1652R1 Printf corner cases in std::format - LWG 3250 std::format: # (alternate form) for NaN and inf - LWG 3243 std::format and negative zeroes Implements parts of: - P0645 Text Formatting Reviewed By: #libc, ldionne, vitaut Differential Revision: https://reviews.llvm.org/D114001
2020-12-15 00:39:15 +08:00
"`3250 <https://wg21.link/LWG3250>`__","``std::format``\ : ``#``\ (alternate form) for NaN and inf","Prague","|Complete|","14.0","|format|"
[libc++][format] Adds formatter pointer. This implements the last required formatter specialization. Completes: - LWG 3251 Are std::format alignment specifiers applied to string arguments? - LWG 3340 Formatting functions should throw on argument/format string mismatch in §[format.functions] - LWG 3540 §[format.arg] There should be no const in basic_format_arg(const T* p) Implements parts of: - P0645 Text Formatting Depends on D114001 Reviewed By: ldionne, vitaut, #libc Differential Revision: https://reviews.llvm.org/D115988
2021-11-28 21:43:43 +08:00
"`3251 <https://wg21.link/LWG3251>`__","Are ``std::format``\ alignment specifiers applied to string arguments?","Prague","|Complete|","14.0","|format|"
[libc++][doc] Adds more issue status labels. A followup to D111458 adding more labels to LWG-issues. This should add the labels for the not completed chrono, format, ranges, and spaceship issues. Some minor formatting cleanups along the way. Reviewed By: #libc, Quuxplusone Differential Revision: https://reviews.llvm.org/D111935
2021-10-16 18:22:25 +08:00
"`3252 <https://wg21.link/LWG3252>`__","Parse locale's aware modifiers for commands are not consistent with POSIX spec","Prague","","","|chrono|"
[libc++] [docs] Add Version column to issues tables on status pages.
2020-12-05 01:41:51 +08:00
"`3254 <https://wg21.link/LWG3254>`__","Strike ``stop_token``\ 's ``operator!=``\ ","Prague","",""
"`3255 <https://wg21.link/LWG3255>`__","``span``\ 's ``array``\ constructor is too strict","Prague","|Complete|",""
[libc++][doc] Adds more issue status labels. A followup to D111458 adding more labels to LWG-issues. This should add the labels for the not completed chrono, format, ranges, and spaceship issues. Some minor formatting cleanups along the way. Reviewed By: #libc, Quuxplusone Differential Revision: https://reviews.llvm.org/D111935
2021-10-16 18:22:25 +08:00
"`3260 <https://wg21.link/LWG3260>`__","``year_month*``\ arithmetic rejects durations convertible to years","Prague","","","|chrono|"
[libc++][doc] Use issue labels. During the review of D111166 I had a private discussion with @ldionne to avoid the duplication of the C++2b issues in the Ranges and Format status pages. The main reason for duplicating them is to make it easier to find them. The title of the paper may not always make it clear to which project the paper belongs. This commit removes all LWG-issues from the Ranges and Format status page and adds labels for these issue in the C++20/C++23 issues list. A quick scan revealed there are some issues that are missing a label since they weren't on the ranges issue list. These can be labelled in a separate commit. In that commit I'll also look for issues for the spaceship operator and chrono. Reviewed By: Quuxplusone, ldionne, #libc Differential Revision: https://reviews.llvm.org/D111458
2021-10-09 03:01:55 +08:00
"`3262 <https://wg21.link/LWG3262>`__","Formatting of negative durations is not specified","Prague","","","|chrono| |format|"
[libc++][doc] Adds more issue status labels. A followup to D111458 adding more labels to LWG-issues. This should add the labels for the not completed chrono, format, ranges, and spaceship issues. Some minor formatting cleanups along the way. Reviewed By: #libc, Quuxplusone Differential Revision: https://reviews.llvm.org/D111935
2021-10-16 18:22:25 +08:00
"`3264 <https://wg21.link/LWG3264>`__","``sized_range``\ and ``ranges::size``\ redundantly use ``disable_sized_range``\ ","Prague","","","|ranges|"
"`3269 <https://wg21.link/LWG3269>`__","Parse manipulators do not specify the result of the extraction from stream","Prague","","","|chrono|"
[libc++][doc] Use issue labels. During the review of D111166 I had a private discussion with @ldionne to avoid the duplication of the C++2b issues in the Ranges and Format status pages. The main reason for duplicating them is to make it easier to find them. The title of the paper may not always make it clear to which project the paper belongs. This commit removes all LWG-issues from the Ranges and Format status page and adds labels for these issue in the C++20/C++23 issues list. A quick scan revealed there are some issues that are missing a label since they weren't on the ranges issue list. These can be labelled in a separate commit. In that commit I'll also look for issues for the spaceship operator and chrono. Reviewed By: Quuxplusone, ldionne, #libc Differential Revision: https://reviews.llvm.org/D111458
2021-10-09 03:01:55 +08:00
"`3270 <https://wg21.link/LWG3270>`__","Parsing and formatting ``%j``\ with ``duration``\ s","Prague","","","|chrono| |format|"
"`3280 <https://wg21.link/LWG3280>`__","View converting constructors can cause constraint recursion and are unneeded","Prague","","","|ranges|"
"`3281 <https://wg21.link/LWG3281>`__","Conversion from ``*pair-like*``\ types to ``subrange``\ is a silent semantic promotion","Prague","","","|ranges|"
"`3282 <https://wg21.link/LWG3282>`__","``subrange``\ converting constructor should disallow derived to base conversions","Prague","","","|ranges|"
[libc++][doc] Adds more issue status labels. A followup to D111458 adding more labels to LWG-issues. This should add the labels for the not completed chrono, format, ranges, and spaceship issues. Some minor formatting cleanups along the way. Reviewed By: #libc, Quuxplusone Differential Revision: https://reviews.llvm.org/D111935
2021-10-16 18:22:25 +08:00
"`3284 <https://wg21.link/LWG3284>`__","``random_access_iterator``\ semantic constraints accidentally promote difference type using unary negate","Prague","","","|ranges|"
[libc++] [docs] Add Version column to issues tables on status pages.
2020-12-05 01:41:51 +08:00
"`3285 <https://wg21.link/LWG3285>`__","The type of a customization point object shall satisfy ``semiregular``\ ","Prague","",""
[libc++][doc] Use issue labels. During the review of D111166 I had a private discussion with @ldionne to avoid the duplication of the C++2b issues in the Ranges and Format status pages. The main reason for duplicating them is to make it easier to find them. The title of the paper may not always make it clear to which project the paper belongs. This commit removes all LWG-issues from the Ranges and Format status page and adds labels for these issue in the C++20/C++23 issues list. A quick scan revealed there are some issues that are missing a label since they weren't on the ranges issue list. These can be labelled in a separate commit. In that commit I'll also look for issues for the spaceship operator and chrono. Reviewed By: Quuxplusone, ldionne, #libc Differential Revision: https://reviews.llvm.org/D111458
2021-10-09 03:01:55 +08:00
"`3286 <https://wg21.link/LWG3286>`__","``ranges::size``\ is not required to be valid after a call to ``ranges::begin``\ on an input range","Prague","","","|ranges|"
"`3291 <https://wg21.link/LWG3291>`__","``iota_view::iterator``\ has the wrong ``iterator_category``\ ","Prague","","","|ranges|"
"`3292 <https://wg21.link/LWG3292>`__","``iota_view``\ is under-constrained","Prague","","","|ranges|"
[libc++][doc] Adds more issue status labels. A followup to D111458 adding more labels to LWG-issues. This should add the labels for the not completed chrono, format, ranges, and spaceship issues. Some minor formatting cleanups along the way. Reviewed By: #libc, Quuxplusone Differential Revision: https://reviews.llvm.org/D111935
2021-10-16 18:22:25 +08:00
"`3294 <https://wg21.link/LWG3294>`__","``zoned_time``\ deduction guides misinterprets ``string``\ /``char*``\ ","Prague","","","|chrono|"
[libc++] [docs] Add Version column to issues tables on status pages.
2020-12-05 01:41:51 +08:00
"`3296 <https://wg21.link/LWG3296>`__","Inconsistent default argument for ``basic_regex<>::assign``\ ","Prague","|Complete|",""
[libc++][doc] Use issue labels. During the review of D111166 I had a private discussion with @ldionne to avoid the duplication of the C++2b issues in the Ranges and Format status pages. The main reason for duplicating them is to make it easier to find them. The title of the paper may not always make it clear to which project the paper belongs. This commit removes all LWG-issues from the Ranges and Format status page and adds labels for these issue in the C++20/C++23 issues list. A quick scan revealed there are some issues that are missing a label since they weren't on the ranges issue list. These can be labelled in a separate commit. In that commit I'll also look for issues for the spaceship operator and chrono. Reviewed By: Quuxplusone, ldionne, #libc Differential Revision: https://reviews.llvm.org/D111458
2021-10-09 03:01:55 +08:00
"`3299 <https://wg21.link/LWG3299>`__","Pointers don't need customized iterator behavior","Prague","","","|ranges|"
[libc++] [docs] Add Version column to issues tables on status pages.
2020-12-05 01:41:51 +08:00
"`3300 <https://wg21.link/LWG3300>`__","Non-array ``ssize``\ overload is underconstrained","Prague","",""
[libc++][doc] Use issue labels. During the review of D111166 I had a private discussion with @ldionne to avoid the duplication of the C++2b issues in the Ranges and Format status pages. The main reason for duplicating them is to make it easier to find them. The title of the paper may not always make it clear to which project the paper belongs. This commit removes all LWG-issues from the Ranges and Format status page and adds labels for these issue in the C++20/C++23 issues list. A quick scan revealed there are some issues that are missing a label since they weren't on the ranges issue list. These can be labelled in a separate commit. In that commit I'll also look for issues for the spaceship operator and chrono. Reviewed By: Quuxplusone, ldionne, #libc Differential Revision: https://reviews.llvm.org/D111458
2021-10-09 03:01:55 +08:00
"`3301 <https://wg21.link/LWG3301>`__","``transform_view::iterator``\ has incorrect ``iterator_category``\ ","Prague","","","|ranges|"
"`3302 <https://wg21.link/LWG3302>`__","Range adaptor objects ``keys``\ and ``values``\ are unspecified","Prague","","","|ranges|"
[libc++] [docs] Add Version column to issues tables on status pages.
2020-12-05 01:41:51 +08:00
"`3303 <https://wg21.link/LWG3303>`__","Bad ""``constexpr``\ "" marker for ``destroy/destroy_n``\ ","Prague","",""
"`3304 <https://wg21.link/LWG3304>`__","Allocate functions of ``std::polymorphic_allocator``\ should require ``[[nodiscard]]``\ ","Prague","",""
"`3307 <https://wg21.link/LWG3307>`__","``std::allocator<void>().allocate(n)``\ ","Prague","",""
"`3310 <https://wg21.link/LWG3310>`__","Replace ``SIZE_MAX``\ with ``numeric_limits<size_t>::max()``\ ","Prague","",""
[libc++][doc] Use issue labels. During the review of D111166 I had a private discussion with @ldionne to avoid the duplication of the C++2b issues in the Ranges and Format status pages. The main reason for duplicating them is to make it easier to find them. The title of the paper may not always make it clear to which project the paper belongs. This commit removes all LWG-issues from the Ranges and Format status page and adds labels for these issue in the C++20/C++23 issues list. A quick scan revealed there are some issues that are missing a label since they weren't on the ranges issue list. These can be labelled in a separate commit. In that commit I'll also look for issues for the spaceship operator and chrono. Reviewed By: Quuxplusone, ldionne, #libc Differential Revision: https://reviews.llvm.org/D111458
2021-10-09 03:01:55 +08:00
"`3313 <https://wg21.link/LWG3313>`__","``join_view::iterator::operator--``\ is incorrectly constrained","Prague","","","|ranges|"
[libc++][doc] Adds more issue status labels. A followup to D111458 adding more labels to LWG-issues. This should add the labels for the not completed chrono, format, ranges, and spaceship issues. Some minor formatting cleanups along the way. Reviewed By: #libc, Quuxplusone Differential Revision: https://reviews.llvm.org/D111935
2021-10-16 18:22:25 +08:00
"`3314 <https://wg21.link/LWG3314>`__","Is stream insertion behavior locale dependent when ``Period::type``\ is ``micro``\ ?","Prague","","","|chrono|"
[libc++] [docs] Add Version column to issues tables on status pages.
2020-12-05 01:41:51 +08:00
"`3315 <https://wg21.link/LWG3315>`__","Correct Allocator Default Behavior","Prague","",""
[libc++][doc] Adds more issue status labels. A followup to D111458 adding more labels to LWG-issues. This should add the labels for the not completed chrono, format, ranges, and spaceship issues. Some minor formatting cleanups along the way. Reviewed By: #libc, Quuxplusone Differential Revision: https://reviews.llvm.org/D111935
2021-10-16 18:22:25 +08:00
"`3316 <https://wg21.link/LWG3316>`__","Correctly define epoch for ``utc_clock``\ / ``utc_timepoint``\ ","Prague","","","|chrono|"
"`3317 <https://wg21.link/LWG3317>`__","Incorrect ``operator<<``\ for floating-point durations","Prague","","","|chrono|"
"`3318 <https://wg21.link/LWG3318>`__","Clarify whether clocks can represent time before their epoch","Prague","","","|chrono|"
"`3319 <https://wg21.link/LWG3319>`__","Properly reference specification of IANA time zone database","Prague","","","|chrono|"
[libc++] [docs] Add Version column to issues tables on status pages.
2020-12-05 01:41:51 +08:00
"`3320 <https://wg21.link/LWG3320>`__","``span::cbegin/cend``\ methods produce different results than ``std::[ranges::]cbegin/cend``\ ","Prague","|Complete|",""
"`3321 <https://wg21.link/LWG3321>`__","``uninitialized_construct_using_allocator``\ should use ``construct_at``\ ","Prague","",""
[libc++][doc] Use issue labels. During the review of D111166 I had a private discussion with @ldionne to avoid the duplication of the C++2b issues in the Ranges and Format status pages. The main reason for duplicating them is to make it easier to find them. The title of the paper may not always make it clear to which project the paper belongs. This commit removes all LWG-issues from the Ranges and Format status page and adds labels for these issue in the C++20/C++23 issues list. A quick scan revealed there are some issues that are missing a label since they weren't on the ranges issue list. These can be labelled in a separate commit. In that commit I'll also look for issues for the spaceship operator and chrono. Reviewed By: Quuxplusone, ldionne, #libc Differential Revision: https://reviews.llvm.org/D111458
2021-10-09 03:01:55 +08:00
"`3323 <https://wg21.link/LWG3323>`__","``*has-tuple-element*``\ helper concept needs ``convertible_to``\ ","Prague","","","|ranges|"
[libc++] [P1614] Implement [cmp.alg]'s std::{strong,weak,partial}_order. This does not include `std::compare_*_fallback`; those are coming later. There's still an open question of how to implement std::strong_order for `long double`, which has 80 value bits and 48 padding bits on x86-64, and which is presumably *not* IEEE 754-compliant on PPC64 and so on. So that part is left unimplemented. Differential Revision: https://reviews.llvm.org/D110738
2021-07-29 10:04:18 +08:00
"`3324 <https://wg21.link/LWG3324>`__","Special-case ``std::strong/weak/partial_order``\ for pointers","Prague","|Complete|","14.0","|spaceship|"
[libc++][doc] Use issue labels. During the review of D111166 I had a private discussion with @ldionne to avoid the duplication of the C++2b issues in the Ranges and Format status pages. The main reason for duplicating them is to make it easier to find them. The title of the paper may not always make it clear to which project the paper belongs. This commit removes all LWG-issues from the Ranges and Format status page and adds labels for these issue in the C++20/C++23 issues list. A quick scan revealed there are some issues that are missing a label since they weren't on the ranges issue list. These can be labelled in a separate commit. In that commit I'll also look for issues for the spaceship operator and chrono. Reviewed By: Quuxplusone, ldionne, #libc Differential Revision: https://reviews.llvm.org/D111458
2021-10-09 03:01:55 +08:00
"`3325 <https://wg21.link/LWG3325>`__","Constrain return type of transformation function for ``transform_view``\ ","Prague","","","|ranges|"
[libc++][doc] Adds more issue status labels. A followup to D111458 adding more labels to LWG-issues. This should add the labels for the not completed chrono, format, ranges, and spaceship issues. Some minor formatting cleanups along the way. Reviewed By: #libc, Quuxplusone Differential Revision: https://reviews.llvm.org/D111935
2021-10-16 18:22:25 +08:00
"`3326 <https://wg21.link/LWG3326>`__","``enable_view``\ has false positives","Prague","|In progress|","","|ranges|"
[libc++][doc] Use issue labels. During the review of D111166 I had a private discussion with @ldionne to avoid the duplication of the C++2b issues in the Ranges and Format status pages. The main reason for duplicating them is to make it easier to find them. The title of the paper may not always make it clear to which project the paper belongs. This commit removes all LWG-issues from the Ranges and Format status page and adds labels for these issue in the C++20/C++23 issues list. A quick scan revealed there are some issues that are missing a label since they weren't on the ranges issue list. These can be labelled in a separate commit. In that commit I'll also look for issues for the spaceship operator and chrono. Reviewed By: Quuxplusone, ldionne, #libc Differential Revision: https://reviews.llvm.org/D111458
2021-10-09 03:01:55 +08:00
"`3327 <https://wg21.link/LWG3327>`__","Format alignment specifiers vs. text direction","Prague","|Nothing To Do|","","|format|"
[libc++] [docs] Add Version column to issues tables on status pages.
2020-12-05 01:41:51 +08:00
"`3328 <https://wg21.link/LWG3328>`__","Clarify that ``std::string``\ is not good for UTF-8","Prague","",""
[libcxx] adds __cpp_lib_concepts feature-test macro Also adjusts C++20 status paper to indicate full concepts support. Depends on D96477, D99817. Differential Revision: https://reviews.llvm.org/D99805
2021-04-03 02:07:31 +08:00
"`3329 <https://wg21.link/LWG3329>`__","``totally_ordered_with``\ both directly and indirectly requires ``common_reference_with``\ ","Prague","|Complete|","13.0"
[libc++] [doc] Mark some spaceship-related LWG issues as "Complete." LWG3330 has been "Completed" since D99309, which was in the 13.x timeframe. Reviewed as part of D110738.
2021-10-15 04:49:58 +08:00
"`3330 <https://wg21.link/LWG3330>`__","Include ``<compare>``\ from most library headers","Prague","|Complete|","13.0","|spaceship|"
[libc++][doc] Adds more issue status labels. A followup to D111458 adding more labels to LWG-issues. This should add the labels for the not completed chrono, format, ranges, and spaceship issues. Some minor formatting cleanups along the way. Reviewed By: #libc, Quuxplusone Differential Revision: https://reviews.llvm.org/D111935
2021-10-16 18:22:25 +08:00
"`3331 <https://wg21.link/LWG3331>`__","Define ``totally_ordered/_with``\ in terms of ``partially-ordered-with``\ ","Prague","|Complete|","13.0"
[libc++][doc] Use issue labels. During the review of D111166 I had a private discussion with @ldionne to avoid the duplication of the C++2b issues in the Ranges and Format status pages. The main reason for duplicating them is to make it easier to find them. The title of the paper may not always make it clear to which project the paper belongs. This commit removes all LWG-issues from the Ranges and Format status page and adds labels for these issue in the C++20/C++23 issues list. A quick scan revealed there are some issues that are missing a label since they weren't on the ranges issue list. These can be labelled in a separate commit. In that commit I'll also look for issues for the spaceship operator and chrono. Reviewed By: Quuxplusone, ldionne, #libc Differential Revision: https://reviews.llvm.org/D111458
2021-10-09 03:01:55 +08:00
"`3332 <https://wg21.link/LWG3332>`__","Issue in |sect|\ [time.format]","Prague","","","|chrono| |format|"
[libc++] [docs] Add Version column to issues tables on status pages.
2020-12-05 01:41:51 +08:00
"`3334 <https://wg21.link/LWG3334>`__","``basic_osyncstream``\ move assignment and destruction calls ``basic_syncbuf::emit()``\ twice","Prague","",""
[libc++][doc] Use issue labels. During the review of D111166 I had a private discussion with @ldionne to avoid the duplication of the C++2b issues in the Ranges and Format status pages. The main reason for duplicating them is to make it easier to find them. The title of the paper may not always make it clear to which project the paper belongs. This commit removes all LWG-issues from the Ranges and Format status page and adds labels for these issue in the C++20/C++23 issues list. A quick scan revealed there are some issues that are missing a label since they weren't on the ranges issue list. These can be labelled in a separate commit. In that commit I'll also look for issues for the spaceship operator and chrono. Reviewed By: Quuxplusone, ldionne, #libc Differential Revision: https://reviews.llvm.org/D111458
2021-10-09 03:01:55 +08:00
"`3335 <https://wg21.link/LWG3335>`__","Resolve C++20 NB comments US 273 and GB 274","Prague","","","|ranges|"
[libcxx] adds __cpp_lib_concepts feature-test macro Also adjusts C++20 status paper to indicate full concepts support. Depends on D96477, D99817. Differential Revision: https://reviews.llvm.org/D99805
2021-04-03 02:07:31 +08:00
"`3338 <https://wg21.link/LWG3338>`__","Rename ``default_constructible``\ to ``default_initializable``\ ","Prague","|Complete|","13.0"
[libc++][format] Adds formatter pointer. This implements the last required formatter specialization. Completes: - LWG 3251 Are std::format alignment specifiers applied to string arguments? - LWG 3340 Formatting functions should throw on argument/format string mismatch in §[format.functions] - LWG 3540 §[format.arg] There should be no const in basic_format_arg(const T* p) Implements parts of: - P0645 Text Formatting Depends on D114001 Reviewed By: ldionne, vitaut, #libc Differential Revision: https://reviews.llvm.org/D115988
2021-11-28 21:43:43 +08:00
"`3340 <https://wg21.link/LWG3340>`__","Formatting functions should throw on argument/format string mismatch in |sect|\ [format.functions]","Prague","|Complete|","14.0","|format|"
[libc++] [docs] Add Version column to issues tables on status pages.
2020-12-05 01:41:51 +08:00
"`3346 <https://wg21.link/LWG3346>`__","``pair``\ and ``tuple``\ copy and move constructor have backwards specification","Prague","",""
"`3347 <https://wg21.link/LWG3347>`__","``std::pair<T, U>``\ now requires ``T``\ and ``U``\ to be less-than-comparable","Prague","",""
[libcxx][docs] Mark LWG3356 as complete Feature test macro for `__cpp_lib_is_nothrow_convertible` was introduced in 466df1718e41fe2fca6ce6bd98c01b18f42c05e4 but the LWG issue was not marked as `Complete` in the docs. Also, fix the formatting of `Complete` for LWG 3348. Reviewed By: ldionne, #libc Differential Revision: https://reviews.llvm.org/D108964
2021-09-01 20:19:30 +08:00
"`3348 <https://wg21.link/LWG3348>`__","``__cpp_lib_unwrap_ref``\ in wrong header","Prague","|Complete|","12.0"
[libc++] [docs] Add Version column to issues tables on status pages.
2020-12-05 01:41:51 +08:00
"`3349 <https://wg21.link/LWG3349>`__","Missing ``__cpp_lib_constexpr_complex``\ for P0415R1","Prague","",""
[libc++][doc] Adds more issue status labels. A followup to D111458 adding more labels to LWG-issues. This should add the labels for the not completed chrono, format, ranges, and spaceship issues. Some minor formatting cleanups along the way. Reviewed By: #libc, Quuxplusone Differential Revision: https://reviews.llvm.org/D111935
2021-10-16 18:22:25 +08:00
"`3350 <https://wg21.link/LWG3350>`__","Simplify return type of ``lexicographical_compare_three_way``\ ","Prague","","","|spaceship|"
"`3351 <https://wg21.link/LWG3351>`__","``ranges::enable_safe_range``\ should not be constrained","Prague","","","|ranges|"
[libc++] [doc] Mark some spaceship-related LWG issues as "Complete." LWG3330 has been "Completed" since D99309, which was in the 13.x timeframe. Reviewed as part of D110738.
2021-10-15 04:49:58 +08:00
"`3352 <https://wg21.link/LWG3352>`__","``strong_equality``\ isn't a thing","Prague","|Nothing To Do|","","|spaceship|"
[libc++][doc] Adds more issue status labels. A followup to D111458 adding more labels to LWG-issues. This should add the labels for the not completed chrono, format, ranges, and spaceship issues. Some minor formatting cleanups along the way. Reviewed By: #libc, Quuxplusone Differential Revision: https://reviews.llvm.org/D111935
2021-10-16 18:22:25 +08:00
"`3354 <https://wg21.link/LWG3354>`__","``has_strong_structural_equality``\ has a meaningless definition","Prague","","","|spaceship|"
[libc++][doc] Use issue labels. During the review of D111166 I had a private discussion with @ldionne to avoid the duplication of the C++2b issues in the Ranges and Format status pages. The main reason for duplicating them is to make it easier to find them. The title of the paper may not always make it clear to which project the paper belongs. This commit removes all LWG-issues from the Ranges and Format status page and adds labels for these issue in the C++20/C++23 issues list. A quick scan revealed there are some issues that are missing a label since they weren't on the ranges issue list. These can be labelled in a separate commit. In that commit I'll also look for issues for the spaceship operator and chrono. Reviewed By: Quuxplusone, ldionne, #libc Differential Revision: https://reviews.llvm.org/D111458
2021-10-09 03:01:55 +08:00
"`3355 <https://wg21.link/LWG3355>`__","The memory algorithms should support move-only input iterators introduced by P1207","Prague","","","|ranges|"
[libcxx][docs] Mark LWG3356 as complete Feature test macro for `__cpp_lib_is_nothrow_convertible` was introduced in 466df1718e41fe2fca6ce6bd98c01b18f42c05e4 but the LWG issue was not marked as `Complete` in the docs. Also, fix the formatting of `Complete` for LWG 3348. Reviewed By: ldionne, #libc Differential Revision: https://reviews.llvm.org/D108964
2021-09-01 20:19:30 +08:00
"`3356 <https://wg21.link/LWG3356>`__","``__cpp_lib_nothrow_convertible``\ should be ``__cpp_lib_is_nothrow_convertible``\ ","Prague","|Complete|","12.0"
[libc++] [docs] Add Version column to issues tables on status pages.
2020-12-05 01:41:51 +08:00
"`3358 <https://wg21.link/LWG3358>`__","|sect|\ [span.cons] is mistaken that ``to_address``\ can throw","Prague","",""
[libc++][doc] Adds more issue status labels. A followup to D111458 adding more labels to LWG-issues. This should add the labels for the not completed chrono, format, ranges, and spaceship issues. Some minor formatting cleanups along the way. Reviewed By: #libc, Quuxplusone Differential Revision: https://reviews.llvm.org/D111935
2021-10-16 18:22:25 +08:00
"`3359 <https://wg21.link/LWG3359>`__","``<chrono>``\ leap second support should allow for negative leap seconds","Prague","","","|chrono|"
[libc++] [doc] Mark some spaceship-related LWG issues as "Complete." LWG3330 has been "Completed" since D99309, which was in the 13.x timeframe. Reviewed as part of D110738.
2021-10-15 04:49:58 +08:00
"`3360 <https://wg21.link/LWG3360>`__","``three_way_comparable_with``\ is inconsistent with similar concepts","Prague","|Nothing To Do|","","|spaceship|"
[libc++] [docs] Add Version column to issues tables on status pages.
2020-12-05 01:41:51 +08:00
"`3362 <https://wg21.link/LWG3362>`__","Strike ``stop_source``\ 's ``operator!=``\ ","Prague","",""
[libc++][doc] Use issue labels. During the review of D111166 I had a private discussion with @ldionne to avoid the duplication of the C++2b issues in the Ranges and Format status pages. The main reason for duplicating them is to make it easier to find them. The title of the paper may not always make it clear to which project the paper belongs. This commit removes all LWG-issues from the Ranges and Format status page and adds labels for these issue in the C++20/C++23 issues list. A quick scan revealed there are some issues that are missing a label since they weren't on the ranges issue list. These can be labelled in a separate commit. In that commit I'll also look for issues for the spaceship operator and chrono. Reviewed By: Quuxplusone, ldionne, #libc Differential Revision: https://reviews.llvm.org/D111458
2021-10-09 03:01:55 +08:00
"`3363 <https://wg21.link/LWG3363>`__","``drop_while_view``\ should opt-out of ``sized_range``\ ","Prague","","","|ranges|"
"`3364 <https://wg21.link/LWG3364>`__","Initialize data members of ranges and their iterators","Prague","","","|ranges|"
[libc++] [docs] Add Version column to issues tables on status pages.
2020-12-05 01:41:51 +08:00
"`3367 <https://wg21.link/LWG3367>`__","Integer-class conversions should not throw","Prague","",""
[libc++] Implement LWG3369, tweak CTAD for std::span. The original bug doesn't reproduce on Clang, allegedly because of https://bugs.llvm.org/show_bug.cgi?id=44484 We already test STL's exact test case, in "span.cons/deduct.pass.cpp", which I'm touching just for the heck of it. Differential Revision: https://reviews.llvm.org/D111838
2021-10-15 05:02:43 +08:00
"`3369 <https://wg21.link/LWG3369>`__","``span``\ 's deduction-guide for built-in arrays doesn't work","Prague","|Complete|","14.0"
[libc++][doc] Use issue labels. During the review of D111166 I had a private discussion with @ldionne to avoid the duplication of the C++2b issues in the Ranges and Format status pages. The main reason for duplicating them is to make it easier to find them. The title of the paper may not always make it clear to which project the paper belongs. This commit removes all LWG-issues from the Ranges and Format status page and adds labels for these issue in the C++20/C++23 issues list. A quick scan revealed there are some issues that are missing a label since they weren't on the ranges issue list. These can be labelled in a separate commit. In that commit I'll also look for issues for the spaceship operator and chrono. Reviewed By: Quuxplusone, ldionne, #libc Differential Revision: https://reviews.llvm.org/D111458
2021-10-09 03:01:55 +08:00
"`3371 <https://wg21.link/LWG3371>`__","``visit_format_arg``\ and ``make_format_args``\ are not hidden friends","Prague","|Complete|","14.0","|format|"
[libc++][doc] Don't mention Prague twice.
2021-11-07 23:21:05 +08:00
"`3372 <https://wg21.link/LWG3372>`__","``vformat_to``\ should not try to deduce ``Out``\ twice","Prague","|Complete|","14.0","|format|"
[libc++] Adds tests for LWG-3373. The code in libc++ already satisfy the requirements of LWG-3373. Since the issue was written to specifically allow the types to be used in structured bindings, tests have been added to validate the new requirement. Implements LWG-3373 {to,from}_chars_result and format_to_n_result need the "we really mean what we say" wording Reviewed By: #libc, ldionne Differential Revision: https://reviews.llvm.org/D117337
2021-11-09 04:16:50 +08:00
"`3373 <https://wg21.link/LWG3373>`__","``{to,from}_chars_result``\ and ``format_to_n_result``\ need the ""we really mean what we say"" wording","Prague","|Complete|","14.0","|format|"
[libc++] [LWG3374] Mark `to_address(const Ptr& p)` overload `constexpr`. Reviewed By: ldionne, #libc Differential Revision: https://reviews.llvm.org/D92659
2020-12-06 22:23:46 +08:00
"`3374 <https://wg21.link/LWG3374>`__","P0653 + P1006 should have made the other ``std::to_address``\ overload ``constexpr``\ ","Prague","|Complete|","12.0"
[libc++][doc] Adds more issue status labels. A followup to D111458 adding more labels to LWG-issues. This should add the labels for the not completed chrono, format, ranges, and spaceship issues. Some minor formatting cleanups along the way. Reviewed By: #libc, Quuxplusone Differential Revision: https://reviews.llvm.org/D111935
2021-10-16 18:22:25 +08:00
"`3375 <https://wg21.link/LWG3375>`__","``decay``\ in ``viewable_range``\ should be ``remove_cvref``\ ","Prague","","","|ranges|"
"`3377 <https://wg21.link/LWG3377>`__","``elements_view::iterator``\ befriends a specialization of itself","Prague","","","|ranges|"
[libc++] Implements ranges::enable_borrowed_range This is the initial patch to implement ranges in libc++. Implements parts of: - P0896R4 One Ranges Proposal - P1870 forwarding-range is too subtle - LWG3379 in several library names is misleading Reviewed By: ldionne, #libc, cjdb, zoecarver, Quuxplusone Differential Revision: https://reviews.llvm.org/D90999
2020-11-25 01:08:02 +08:00
"`3379 <https://wg21.link/LWG3379>`__","""``safe``\ "" in several library names is misleading","Prague","|In Progress|",""
[libc++][doc] Adds more issue status labels. A followup to D111458 adding more labels to LWG-issues. This should add the labels for the not completed chrono, format, ranges, and spaceship issues. Some minor formatting cleanups along the way. Reviewed By: #libc, Quuxplusone Differential Revision: https://reviews.llvm.org/D111935
2021-10-16 18:22:25 +08:00
"`3380 <https://wg21.link/LWG3380>`__","``common_type``\ and comparison categories","Prague","","","|spaceship|"
[libc++][doc] Use issue labels. During the review of D111166 I had a private discussion with @ldionne to avoid the duplication of the C++2b issues in the Ranges and Format status pages. The main reason for duplicating them is to make it easier to find them. The title of the paper may not always make it clear to which project the paper belongs. This commit removes all LWG-issues from the Ranges and Format status page and adds labels for these issue in the C++20/C++23 issues list. A quick scan revealed there are some issues that are missing a label since they weren't on the ranges issue list. These can be labelled in a separate commit. In that commit I'll also look for issues for the spaceship operator and chrono. Reviewed By: Quuxplusone, ldionne, #libc Differential Revision: https://reviews.llvm.org/D111458
2021-10-09 03:01:55 +08:00
"`3381 <https://wg21.link/LWG3381>`__","``begin``\ and ``data``\ must agree for ``contiguous_range``\ ","Prague","","","|ranges|"
[libc++] [docs] Add Version column to issues tables on status pages.
2020-12-05 01:41:51 +08:00
"`3382 <https://wg21.link/LWG3382>`__","NTTP for ``pair``\ and ``array``\ ","Prague","",""
[libc++][doc] Adds more issue status labels. A followup to D111458 adding more labels to LWG-issues. This should add the labels for the not completed chrono, format, ranges, and spaceship issues. Some minor formatting cleanups along the way. Reviewed By: #libc, Quuxplusone Differential Revision: https://reviews.llvm.org/D111935
2021-10-16 18:22:25 +08:00
"`3383 <https://wg21.link/LWG3383>`__","|sect|\ [time.zone.leap.nonmembers] ``sys_seconds``\ should be replaced with ``seconds``\ ","Prague","","","|chrono|"
[libc++][doc] Use issue labels. During the review of D111166 I had a private discussion with @ldionne to avoid the duplication of the C++2b issues in the Ranges and Format status pages. The main reason for duplicating them is to make it easier to find them. The title of the paper may not always make it clear to which project the paper belongs. This commit removes all LWG-issues from the Ranges and Format status page and adds labels for these issue in the C++20/C++23 issues list. A quick scan revealed there are some issues that are missing a label since they weren't on the ranges issue list. These can be labelled in a separate commit. In that commit I'll also look for issues for the spaceship operator and chrono. Reviewed By: Quuxplusone, ldionne, #libc Differential Revision: https://reviews.llvm.org/D111458
2021-10-09 03:01:55 +08:00
"`3384 <https://wg21.link/LWG3384>`__","``transform_view::*sentinel*``\ has an incorrect ``operator-``\ ","Prague","","","|ranges|"
"`3385 <https://wg21.link/LWG3385>`__","``common_iterator``\ is not sufficiently constrained for non-copyable iterators","Prague","","","|ranges|"
"`3387 <https://wg21.link/LWG3387>`__","|sect|\ [range.reverse.view] ``reverse_view<V>``\ unintentionally requires ``range<const V>``\ ","Prague","","","|ranges|"
"`3388 <https://wg21.link/LWG3388>`__","``view``\ iterator types have ill-formed ``<=>``\ operators","Prague","","","|ranges|"
"`3389 <https://wg21.link/LWG3389>`__","A move-only iterator still does not have a ``counted_iterator``\ ","Prague","","","|ranges|"
[libc++] Fix LWG3390: move_iterator now handles move-only iterators. This can't really be tested until C++20 move_iterator is completely implemented. Differential Revision: https://reviews.llvm.org/D117327
2022-01-15 00:25:56 +08:00
"`3390 <https://wg21.link/LWG3390>`__","``make_move_iterator()``\ cannot be used to construct a ``move_iterator``\ for a move-only iterator","Prague","|Complete|","14.0","|ranges|"
[libcxx] [Coroutine] Conform Coroutine Implementation Since coroutine is merged in C++ standard and the support for coroutine seems relatively stable. It's the time to move the implementation of coroutine out of the experimental directory and the std::experimental namespace. This patch creates header <coroutine> with conformed implementation with C++ standard. To avoid breaking user's code too fast, the <experimental/coroutine> header is remained. Note that <experimental/coroutine> is deprecated and it would be removed in LLVM15. Reviewed By: Quuxplusone, ldionne Differential Revision: https://reviews.llvm.org/D109433
2021-11-16 14:05:34 +08:00
"`3393 <https://wg21.link/LWG3393>`__","Missing/incorrect feature test macro for coroutines","Prague","|Complete|","14.0"
[libc++][doc] Adds more issue status labels. A followup to D111458 adding more labels to LWG-issues. This should add the labels for the not completed chrono, format, ranges, and spaceship issues. Some minor formatting cleanups along the way. Reviewed By: #libc, Quuxplusone Differential Revision: https://reviews.llvm.org/D111935
2021-10-16 18:22:25 +08:00
"`3395 <https://wg21.link/LWG3395>`__","Definition for three-way comparison needs to be updated (US 152)","Prague","","","|spaceship|"
[libc++] [docs] Add Version column to issues tables on status pages.
2020-12-05 01:41:51 +08:00
"`3396 <https://wg21.link/LWG3396>`__","Clarify point of reference for ``source_location::current()``\ (DE 169)","Prague","",""
[libc++][doc] Use issue labels. During the review of D111166 I had a private discussion with @ldionne to avoid the duplication of the C++2b issues in the Ranges and Format status pages. The main reason for duplicating them is to make it easier to find them. The title of the paper may not always make it clear to which project the paper belongs. This commit removes all LWG-issues from the Ranges and Format status page and adds labels for these issue in the C++20/C++23 issues list. A quick scan revealed there are some issues that are missing a label since they weren't on the ranges issue list. These can be labelled in a separate commit. In that commit I'll also look for issues for the spaceship operator and chrono. Reviewed By: Quuxplusone, ldionne, #libc Differential Revision: https://reviews.llvm.org/D111458
2021-10-09 03:01:55 +08:00
"`3397 <https://wg21.link/LWG3397>`__","``ranges::basic_istream_view::iterator``\ should not provide ``iterator_category``\ ","Prague","","","|ranges|"
[libc++] [doc] Mark LWG3398 as complete. This was done in D108054.
2021-10-30 04:12:59 +08:00
"`3398 <https://wg21.link/LWG3398>`__","``tuple_element_t``\ is also wrong for ``const subrange``\ ","Prague","|Complete|","14.0","|ranges|"
[libcxx] adds `std::indirectly_readable_traits` to <iterator> Implements parts of: * P0896R4 The One Ranges Proposal * LWG3446 `indirectly_readable_traits` ambiguity for types with both `value_type` and `element_type` Depends on D99141. Differential Revision: https://reviews.llvm.org/D99461
2021-03-24 04:48:41 +08:00
"`3446 <https://wg21.link/LWG3446>`__","``indirectly_readable_traits``\ ambiguity for types with both ``value_type``\ and ``element_type``\ ","November virtual meeting","|Complete|","13.0"