mirrors/llvm-project
0
0
Fork 0
mirror of https://github.com/llvm/llvm-project.git synced 2025-04-30 02:26:07 +00:00
Code Issues Projects Releases Wiki Activity
llvm-project/libcxx/docs/Status/Cxx2bIssues.csv

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

194 lines
26 KiB
CSV
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-08 21:01:55 +02:00
"Issue #","Issue Name","Meeting","Status","First released version","Labels"
[libc++] [NFC] Audit LWG issues for "Nothing To Do" and "Complete". Each "Nothing To Do" issue only changed nits in the English wording, not anything to do with the code. Each "Complete" issue was completed already, as far as I can tell. I tried to err on the side of caution: I didn't mark a few issues whose P/Rs were very invasive and would take time to verify, and I didn't mark a lot of issues involving features we haven't even started yet. Differential Revision: https://reviews.llvm.org/D117960
2022-01-22 12:26:27 -05:00
"`2839 <https://wg21.link/LWG2839>`__","Self-move-assignment of library types, again","November 2020","|Nothing To Do|",""
[libc++] [docs] [C++2b] Update status page with issues (and forgotten papers) adopted in November 2020 and February 2021 virtual meetings. Sources: * https://github.com/cplusplus/draft/pull/4380 (November 2020) * https://github.com/cplusplus/draft/pull/4523 (February 2021) * https://github.com/cplusplus/draft/issues?q=is%3Aissue+LWG+Motion
2021-03-01 10:31:29 +01:00
"`3117 <https://wg21.link/LWG3117>`__","Missing ``packaged_task`` deduction guides","November 2020","",""
"`3143 <https://wg21.link/LWG3143>`__","``monotonic_buffer_resource`` growth policy is unclear","November 2020","",""
[libc++] [NFC] Audit LWG issues for "Nothing To Do" and "Complete". Each "Nothing To Do" issue only changed nits in the English wording, not anything to do with the code. Each "Complete" issue was completed already, as far as I can tell. I tried to err on the side of caution: I didn't mark a few issues whose P/Rs were very invasive and would take time to verify, and I didn't mark a lot of issues involving features we haven't even started yet. Differential Revision: https://reviews.llvm.org/D117960
2022-01-22 12:26:27 -05:00
"`3195 <https://wg21.link/LWG3195>`__","What is the stored pointer value of an empty ``weak_ptr``?","November 2020","|Nothing To Do|",""
[libc++] Mark LWG3211 as complete: default constructor of tuple<> should be trivial `libc++` has had the guarantee of the default constructor of `tuple<>` being trivial since 405570dc7a95cdf43cdee14b8a9f9c1657a6ad13. Now, the standard mandates it as of LWG3211. So, move the file out of `libcxx/test/libcxx` and into `libcxx/test/std` since it's no longer `libc++`-specific. Rename it to be `.compile.pass.cpp` instead of `.pass.cpp` while we're at it. Reviewed By: ldionne, Quuxplusone, Mordante, #libc Differential Revision: https://reviews.llvm.org/D112743
2021-10-29 12:07:35 -04:00
"`3211 <https://wg21.link/LWG3211>`__","``std::tuple<>`` should be trivially constructible","November 2020","|Complete|","9.0"
[libc++] [NFC] Audit LWG issues for "Nothing To Do" and "Complete". Each "Nothing To Do" issue only changed nits in the English wording, not anything to do with the code. Each "Complete" issue was completed already, as far as I can tell. I tried to err on the side of caution: I didn't mark a few issues whose P/Rs were very invasive and would take time to verify, and I didn't mark a lot of issues involving features we haven't even started yet. Differential Revision: https://reviews.llvm.org/D117960
2022-01-22 12:26:27 -05:00
"`3236 <https://wg21.link/LWG3236>`__","Random access iterator requirements lack limiting relational operators domain to comparing those from the same range","November 2020","|Nothing To Do|","","|ranges|"
[libc++] [docs] [C++2b] Update status page with issues (and forgotten papers) adopted in November 2020 and February 2021 virtual meetings. Sources: * https://github.com/cplusplus/draft/pull/4380 (November 2020) * https://github.com/cplusplus/draft/pull/4523 (February 2021) * https://github.com/cplusplus/draft/issues?q=is%3Aissue+LWG+Motion
2021-03-01 10:31:29 +01:00
"`3265 <https://wg21.link/LWG3265>`__","``move_iterator``'s conversions are more broken after P1207","November 2020","Fixed by `LWG3435 <https://wg21.link/LWG3435>`__",""
[libc++] Implement LWG3435 (constraints on reverse_iterator and move_iterator)
2021-06-03 14:14:57 -04:00
"`3435 <https://wg21.link/LWG3435>`__","``three_way_comparable_with<reverse_iterator<int*>, reverse_iterator<const int*>>``","November 2020","|Complete|","13.0"
[libc++] Uses operator<=> in string_view Implements: - LWG3432 Missing requirement for comparison_category Implements part of: - P1614R2 The Mothership has Landed Reviewed By: #libc, ldionne, jloser, philnik Differential Revision: https://reviews.llvm.org/D130295
2022-07-19 07:56:23 +02:00
"`3432 <https://wg21.link/LWG3432>`__","Missing requirement for ``comparison_category``","November 2020","|Complete|","16.0","|spaceship|"
[libc++][docs] Mark LWG3447 as complete Mark LWG3447 as complete since it was not an issue since the original implementation of `take_view` from 0f4b41e038537ab2ab6fa2aa048e55c28a03ab68. Currently, `take_view`'s deduction guide does not constrain the range on the `range` concept. Reviewed By: ldionne, Mordante, #libc Differential Revision: https://reviews.llvm.org/D111501
2021-10-11 21:40:14 -04:00
"`3447 <https://wg21.link/LWG3447>`__","Deduction guides for ``take_view`` and ``drop_view`` have different constraints","November 2020","|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 12:22:25 +02:00
"`3450 <https://wg21.link/LWG3450>`__","The const overloads of ``take_while_view::begin/end`` are underconstrained","November 2020","","","|ranges|"
[libc++] [docs] [C++2b] Update status page with issues (and forgotten papers) adopted in November 2020 and February 2021 virtual meetings. Sources: * https://github.com/cplusplus/draft/pull/4380 (November 2020) * https://github.com/cplusplus/draft/pull/4523 (February 2021) * https://github.com/cplusplus/draft/issues?q=is%3Aissue+LWG+Motion
2021-03-01 10:31:29 +01:00
"`3464 <https://wg21.link/LWG3464>`__","``istream::gcount()`` can overflow","November 2020","",""
[libc++][NFC] Mark LWG2731 as complete Mark LWG2731 as complete. The type alias `mutex_type` is only provided if `scoped_lock` is given one mutex type and it has been implemented that way since the beginning of Clang 5 it seems. There already are tests for verifying existence (and lack thereof) for `mutex_type` type alias depending on the number of mutex types, so there is nothing to do for this LWG issue. Reviewed By: Quuxplusone, Mordante, #libc Differential Revision: https://reviews.llvm.org/D112462
2021-10-26 13:45:52 -04:00
"`2731 <https://wg21.link/LWG2731>`__","Existence of ``lock_guard<MutexTypes...>::mutex_type`` typedef unclear","November 2020","|Complete|","5.0"
[libc++] [NFC] Audit LWG issues for "Nothing To Do" and "Complete". Each "Nothing To Do" issue only changed nits in the English wording, not anything to do with the code. Each "Complete" issue was completed already, as far as I can tell. I tried to err on the side of caution: I didn't mark a few issues whose P/Rs were very invasive and would take time to verify, and I didn't mark a lot of issues involving features we haven't even started yet. Differential Revision: https://reviews.llvm.org/D117960
2022-01-22 12:26:27 -05:00
"`2743 <https://wg21.link/LWG2743>`__","P0083R3 ``node_handle`` private members missing ""exposition only"" comment","November 2020","|Nothing To Do|",""
"`2820 <https://wg21.link/LWG2820>`__","Clarify ``<cstdint>`` macros","November 2020","|Nothing To Do|",""
[libc++] [docs] [C++2b] Update status page with issues (and forgotten papers) adopted in November 2020 and February 2021 virtual meetings. Sources: * https://github.com/cplusplus/draft/pull/4380 (November 2020) * https://github.com/cplusplus/draft/pull/4523 (February 2021) * https://github.com/cplusplus/draft/issues?q=is%3Aissue+LWG+Motion
2021-03-01 10:31:29 +01:00
"`3120 <https://wg21.link/LWG3120>`__","Unclear behavior of ``monotonic_buffer_resource::release()``","November 2020","",""
"`3170 <https://wg21.link/LWG3170>`__","``is_always_equal`` added to ``std::allocator`` makes the standard library treat derived types as always equal","November 2020","",""
"`3036 <https://wg21.link/LWG3036>`__","``polymorphic_allocator::destroy`` is extraneous","November 2020","",""
[libc++] LWG3171: implement operator<< for filesystem::directory_entry. Differential Revision: https://reviews.llvm.org/D116642
2022-01-13 20:44:01 -08:00
"`3171 <https://wg21.link/LWG3171>`__","LWG2989 breaks ``directory_entry`` stream insertion","November 2020","|Complete|","14.0"
[libc++] [NFC] Audit LWG issues for "Nothing To Do" and "Complete". Each "Nothing To Do" issue only changed nits in the English wording, not anything to do with the code. Each "Complete" issue was completed already, as far as I can tell. I tried to err on the side of caution: I didn't mark a few issues whose P/Rs were very invasive and would take time to verify, and I didn't mark a lot of issues involving features we haven't even started yet. Differential Revision: https://reviews.llvm.org/D117960
2022-01-22 12:26:27 -05:00
"`3306 <https://wg21.link/LWG3306>`__","``ranges::advance`` violates its preconditions","November 2020","|Complete|","14.0","|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 12:22:25 +02:00
"`3403 <https://wg21.link/LWG3403>`__","Domain of ``ranges::ssize(E)`` doesn't ``match ranges::size(E)``","November 2020","","","|ranges|"
"`3404 <https://wg21.link/LWG3404>`__","Finish removing subrange's conversions from pair-like","November 2020","","","|ranges|"
[libc++] [NFC] Audit LWG issues for "Nothing To Do" and "Complete". Each "Nothing To Do" issue only changed nits in the English wording, not anything to do with the code. Each "Complete" issue was completed already, as far as I can tell. I tried to err on the side of caution: I didn't mark a few issues whose P/Rs were very invasive and would take time to verify, and I didn't mark a lot of issues involving features we haven't even started yet. Differential Revision: https://reviews.llvm.org/D117960
2022-01-22 12:26:27 -05:00
"`3405 <https://wg21.link/LWG3405>`__","``common_view``'s converting constructor is bad, too","November 2020","|Complete|","14.0","|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 12:22:25 +02:00
"`3406 <https://wg21.link/LWG3406>`__","``elements_view::begin()`` and ``elements_view::end()`` have incompatible constraints","November 2020","","","|ranges|"
[libc++] [NFC] Audit LWG issues for "Nothing To Do" and "Complete". Each "Nothing To Do" issue only changed nits in the English wording, not anything to do with the code. Each "Complete" issue was completed already, as far as I can tell. I tried to err on the side of caution: I didn't mark a few issues whose P/Rs were very invasive and would take time to verify, and I didn't mark a lot of issues involving features we haven't even started yet. Differential Revision: https://reviews.llvm.org/D117960
2022-01-22 12:26:27 -05:00
"`3419 <https://wg21.link/LWG3419>`__","[algorithms.requirements]/15 doesn't reserve as many rights as it intends to","November 2020","|Nothing To Do|",""
[libc++][docs] Mark LWG3420 complete Mark LWG3420 as complete. Currently, the `cpp17_iterator` concept checks that the type looks like an iterator first before checking if it is copyable. Reviewed By: ldionne, Quuxplusone, #libc Differential Revision: https://reviews.llvm.org/D111598
2021-10-19 09:51:08 -04:00
"`3420 <https://wg21.link/LWG3420>`__","cpp17-iterator should check that the type looks like an iterator first","November 2020","|Complete|","14.0","|ranges|"
[libc++] [NFC] Audit LWG issues for "Nothing To Do" and "Complete". Each "Nothing To Do" issue only changed nits in the English wording, not anything to do with the code. Each "Complete" issue was completed already, as far as I can tell. I tried to err on the side of caution: I didn't mark a few issues whose P/Rs were very invasive and would take time to verify, and I didn't mark a lot of issues involving features we haven't even started yet. Differential Revision: https://reviews.llvm.org/D117960
2022-01-22 12:26:27 -05:00
"`3421 <https://wg21.link/LWG3421>`__","Imperfect ADL emulation for boolean-testable","November 2020","|Nothing To Do|","","|ranges|"
"`3425 <https://wg21.link/LWG3425>`__","``condition_variable_any`` fails to constrain its Lock parameters","November 2020","|Nothing To Do|",""
[libc++] Implement `operator<=>` for `unique_ptr` Implements part of: - P1614R2 The Mothership has Landed Fixes LWG3426 Reviewed By: #libc, Mordante Differential Revision: https://reviews.llvm.org/D130838
2022-08-06 15:04:38 +02:00
"`3426 <https://wg21.link/LWG3426>`__","``operator<=>(const unique_ptr<T, D>&, nullptr_t)`` can't get no satisfaction","November 2020","|Complete|","16.0","|spaceship|"
[libc++] Implement `operator<=>` for `shared_ptr` Implements part of: * P1614R2 The Mothership has Landed Fixes LWG3427 Reviewed By: #libc, Mordante Differential Revision: https://reviews.llvm.org/D130852
2022-08-03 18:28:48 +02:00
"`3427 <https://wg21.link/LWG3427>`__","``operator<=>(const shared_ptr<T>&, nullptr_t)`` definition ill-formed","November 2020","|Complete|","16.0","|spaceship|"
[libc++] [NFC] Audit LWG issues for "Nothing To Do" and "Complete". Each "Nothing To Do" issue only changed nits in the English wording, not anything to do with the code. Each "Complete" issue was completed already, as far as I can tell. I tried to err on the side of caution: I didn't mark a few issues whose P/Rs were very invasive and would take time to verify, and I didn't mark a lot of issues involving features we haven't even started yet. Differential Revision: https://reviews.llvm.org/D117960
2022-01-22 12:26:27 -05:00
"`3428 <https://wg21.link/LWG3428>`__","``single_view``'s in place constructor should be explicit","November 2020","|Complete|","14.0","|ranges|"
"`3434 <https://wg21.link/LWG3434>`__","``ios_base`` never reclaims memory for iarray and parray","November 2020","|Nothing To Do|",""
[libc++] Fix LWG3437 "__cpp_lib_polymorphic_allocator is in the wrong header" https://cplusplus.github.io/LWG/issue3437 Differential Revision: https://reviews.llvm.org/D117963
2022-01-22 15:24:53 -05:00
"`3437 <https://wg21.link/LWG3437>`__","``__cpp_lib_polymorphic_allocator`` is in the wrong header","November 2020","|Complete|","14.0"
[libc++] [NFC] Audit LWG issues for "Nothing To Do" and "Complete". Each "Nothing To Do" issue only changed nits in the English wording, not anything to do with the code. Each "Complete" issue was completed already, as far as I can tell. I tried to err on the side of caution: I didn't mark a few issues whose P/Rs were very invasive and would take time to verify, and I didn't mark a lot of issues involving features we haven't even started yet. Differential Revision: https://reviews.llvm.org/D117960
2022-01-22 12:26:27 -05:00
"`3446 <https://wg21.link/LWG3446>`__","``indirectly_readable_traits`` ambiguity for types with both ``value_type`` and ``element_type``","November 2020","|Complete|","14.0","|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 12:22:25 +02:00
"`3448 <https://wg21.link/LWG3448>`__","``transform_view``'s ``sentinel<false>`` not comparable with ``iterator<true>``","November 2020","","","|ranges|"
"`3449 <https://wg21.link/LWG3449>`__","``take_view`` and ``take_while_view``'s ``sentinel<false>`` not comparable with their ``const iterator``","November 2020","","","|ranges|"
[libc++] [NFC] Audit LWG issues for "Nothing To Do" and "Complete". Each "Nothing To Do" issue only changed nits in the English wording, not anything to do with the code. Each "Complete" issue was completed already, as far as I can tell. I tried to err on the side of caution: I didn't mark a few issues whose P/Rs were very invasive and would take time to verify, and I didn't mark a lot of issues involving features we haven't even started yet. Differential Revision: https://reviews.llvm.org/D117960
2022-01-22 12:26:27 -05:00
"`3453 <https://wg21.link/LWG3453>`__","Generic code cannot call ``ranges::advance(i, s)``","November 2020","|Nothing To Do|","","|ranges|"
[libc++][nfc] Test std::unique_ptr self move assignment. The post-conditions for the self move assignment of `std::unique_ptr` were changed. This requires no implementation changes. A test was added to validate the new post-conditions. Addresses - LWG-3455: Incorrect Postconditions on `unique_ptr` move assignment Reviewed By: #libc, ldionne Differential Revision: https://reviews.llvm.org/D103764
2021-06-06 13:44:10 +02:00
"`3455 <https://wg21.link/LWG3455>`__","Incorrect Postconditions on ``unique_ptr`` move assignment","November 2020","|Nothing To Do|",""
[libcxx] [Coroutines] Support noop_coroutine for GCC We didn't support noop_coroutine for GCC in previous conforming patch. So that GCC couldn't use noop_coroutine() defined in <coroutine>. And after this patch, GCC should be able to compile the whole <coroutine> header. Reviewed By: Quuxplusone Differential Revision: https://reviews.llvm.org/D116144
2021-12-27 13:52:42 +08:00
"`3460 <https://wg21.link/LWG3460>`__","Unimplementable ``noop_coroutine_handle`` guarantees","November 2020","|Complete|","14.0"
[libc++] [NFC] Audit LWG issues for "Nothing To Do" and "Complete". Each "Nothing To Do" issue only changed nits in the English wording, not anything to do with the code. Each "Complete" issue was completed already, as far as I can tell. I tried to err on the side of caution: I didn't mark a few issues whose P/Rs were very invasive and would take time to verify, and I didn't mark a lot of issues involving features we haven't even started yet. Differential Revision: https://reviews.llvm.org/D117960
2022-01-22 12:26:27 -05:00
"`3461 <https://wg21.link/LWG3461>`__","``convertible_to``'s description mishandles cv-qualified ``void``","November 2020","|Nothing To Do|",""
[libc++] [P1614] Implement the second half of [cmp.alg]: compare_{strong,weak,partial}_fallback. The tests for these are just copy-pasted from the tests for std::{strong,weak,partial}_order, and then I added an extra clause in each (test_2()) to test the stuff that's not just the same as std::*_order. This also includes the fix for https://wg21.link/LWG3465 (which falls naturally out of the "you must write it three times" style, but I've added test cases for it also). There is an action item here to go back and give good diagnostics for SFINAE failures in these CPOs. I've filed this as https://github.com/llvm/llvm-project/issues/53456 . Differential Revision: https://reviews.llvm.org/D111514
2021-09-08 16:48:50 -04:00
"`3465 <https://wg21.link/LWG3465>`__","``compare_partial_order_fallback`` requires ``F < E``","November 2020","|Complete|","14.0","|spaceship|"
[libc++] [NFC] Audit LWG issues for "Nothing To Do" and "Complete". Each "Nothing To Do" issue only changed nits in the English wording, not anything to do with the code. Each "Complete" issue was completed already, as far as I can tell. I tried to err on the side of caution: I didn't mark a few issues whose P/Rs were very invasive and would take time to verify, and I didn't mark a lot of issues involving features we haven't even started yet. Differential Revision: https://reviews.llvm.org/D117960
2022-01-22 12:26:27 -05:00
"`3466 <https://wg21.link/LWG3466>`__","Specify the requirements for ``promise``/``future``/``shared_future`` consistently","November 2020","|Nothing To Do|",""
"`3467 <https://wg21.link/LWG3467>`__","``bool`` can't be an integer-like type","November 2020","|Complete|","14.0"
"`3472 <https://wg21.link/LWG3472>`__","``counted_iterator`` is missing preconditions","November 2020","|Complete|","14.0","|ranges|"
[libc++][format] Improve format-arg-store. This optimizes the __format_arg_store type to allow a more efficient storage of the basic_format_args. It stores the data in two arrays: - A struct with the tag of the exposition only variant's type and the offset of the element in the data array. Since this array only depends on the type information it's calculated at compile time and can be shared by different instances of this class. - The arguments converted to the types used in the exposition only variant of basic_format_arg. This means the packed data can be directly copied to an element of this variant. The new code uses rvalue reference arguments in preparation for P2418. The handle class also has some changes to prepare for P2418. The real changed for P2418 will be done separately, but these parts make it easier to implement that paper. Some parts of existing test code are removed since they were no longer valid after the changes, but new tests have been added. Implements parts of: - P2418 Add support for std::generator-like types to std::format Completes: - LWG3473 Normative encouragement in non-normative note Depends on D121138 Reviewed By: #libc, vitaut, Mordante Differential Revision: https://reviews.llvm.org/D121514
2021-10-03 13:11:53 +02:00
"`3473 <https://wg21.link/LWG3473>`__","Normative encouragement in non-normative note","November 2020","|Complete|","15.0","|format|"
[libcxx][ranges] add views::join adaptor object. added test coverage to join_view - added views::join adaptor object - added test for the adaptor object - fixed some join_view's tests. e.g iter_swap test - added some negative tests for join_view to test that operations do not exist when constraints aren't met - added tests that locks down issues that were already addressed in previous change - LWG3500 `join_view::iterator::operator->()` is bogus - LWG3313 `join_view::iterator::operator--` is incorrectly constrained - LWG3517 `join_view::iterator`'s `iter_swap` is underconstrained - P2328R1 join_view should join all views of ranges - fixed some issues in join_view and added tests - LWG3535 `join_view::iterator::iterator_category` and `::iterator_concept` lie - LWG3474 Nesting ``join_views`` is broken because of CTAD - added tests for an LWG issue that isn't resolved in the standard yet, but the previous code has workaround. - LWG3569 Inner iterator not default_initializable Reviewed By: #libc, var-const Spies: var-const, libcxx-commits Differential Revision: https://reviews.llvm.org/D123466
2022-04-21 13:08:34 +02:00
"`3474 <https://wg21.link/LWG3474>`__","Nesting ``join_views`` is broken because of CTAD","November 2020","|Complete|","15.0","|ranges|"
[libc++] [docs] [C++2b] Update status page with issues (and forgotten papers) adopted in November 2020 and February 2021 virtual meetings. Sources: * https://github.com/cplusplus/draft/pull/4380 (November 2020) * https://github.com/cplusplus/draft/pull/4523 (February 2021) * https://github.com/cplusplus/draft/issues?q=is%3Aissue+LWG+Motion
2021-03-01 10:31:29 +01:00
"`3476 <https://wg21.link/LWG3476>`__","``thread`` and ``jthread`` constructors require that the parameters be move-constructible but never move construct the parameters","November 2020","",""
[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 12:22:25 +02:00
"`3477 <https://wg21.link/LWG3477>`__","Simplify constraints for ``semiregular-box``","November 2020","","","|ranges|"
[libc++] [NFC] Audit LWG issues for "Nothing To Do" and "Complete". Each "Nothing To Do" issue only changed nits in the English wording, not anything to do with the code. Each "Complete" issue was completed already, as far as I can tell. I tried to err on the side of caution: I didn't mark a few issues whose P/Rs were very invasive and would take time to verify, and I didn't mark a lot of issues involving features we haven't even started yet. Differential Revision: https://reviews.llvm.org/D117960
2022-01-22 12:26:27 -05:00
"`3482 <https://wg21.link/LWG3482>`__","``drop_view``'s const begin should additionally require ``sized_range``","November 2020","|Complete|","14.0","|ranges|"
"`3483 <https://wg21.link/LWG3483>`__","``transform_view::iterator``'s difference is overconstrained","November 2020","|Complete|","14.0","|ranges|"
[libc++] [docs] [C++2b] Update status page with issues (and forgotten papers) adopted in November 2020 and February 2021 virtual meetings. Sources: * https://github.com/cplusplus/draft/pull/4380 (November 2020) * https://github.com/cplusplus/draft/pull/4523 (February 2021) * https://github.com/cplusplus/draft/issues?q=is%3Aissue+LWG+Motion
2021-03-01 10:31:29 +01:00
"","","","",""
[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 12:22:25 +02:00
"`3391 <https://wg21.link/LWG3391>`__","Problems with ``counted_iterator``/``move_iterator::base() const &``","February 2021","","","|ranges|"
[libc++] [NFC] Audit LWG issues for "Nothing To Do" and "Complete". Each "Nothing To Do" issue only changed nits in the English wording, not anything to do with the code. Each "Complete" issue was completed already, as far as I can tell. I tried to err on the side of caution: I didn't mark a few issues whose P/Rs were very invasive and would take time to verify, and I didn't mark a lot of issues involving features we haven't even started yet. Differential Revision: https://reviews.llvm.org/D117960
2022-01-22 12:26:27 -05:00
"`3433 <https://wg21.link/LWG3433>`__","``subrange::advance(n)`` has UB when ``n < 0``","February 2021","|Complete|","14.0","|ranges|"
"`3490 <https://wg21.link/LWG3490>`__","``ranges::drop_while_view::begin()`` is missing a precondition","February 2021","|Nothing To Do|","","|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 12:22:25 +02:00
"`3492 <https://wg21.link/LWG3492>`__","Minimal improvements to ``elements_view::iterator``","February 2021","","","|ranges|"
"`3494 <https://wg21.link/LWG3494>`__","Allow ranges to be conditionally borrowed","February 2021","Superseded by `P2017R1 <https://wg21.link/P2017R1>`__","","|ranges|"
[libc++] [NFC] Audit LWG issues for "Nothing To Do" and "Complete". Each "Nothing To Do" issue only changed nits in the English wording, not anything to do with the code. Each "Complete" issue was completed already, as far as I can tell. I tried to err on the side of caution: I didn't mark a few issues whose P/Rs were very invasive and would take time to verify, and I didn't mark a lot of issues involving features we haven't even started yet. Differential Revision: https://reviews.llvm.org/D117960
2022-01-22 12:26:27 -05:00
"`3495 <https://wg21.link/LWG3495>`__","``constexpr launder`` makes pointers to inactive members of unions usable","February 2021","|Nothing To Do|",""
[libcxx][ranges] add views::join adaptor object. added test coverage to join_view - added views::join adaptor object - added test for the adaptor object - fixed some join_view's tests. e.g iter_swap test - added some negative tests for join_view to test that operations do not exist when constraints aren't met - added tests that locks down issues that were already addressed in previous change - LWG3500 `join_view::iterator::operator->()` is bogus - LWG3313 `join_view::iterator::operator--` is incorrectly constrained - LWG3517 `join_view::iterator`'s `iter_swap` is underconstrained - P2328R1 join_view should join all views of ranges - fixed some issues in join_view and added tests - LWG3535 `join_view::iterator::iterator_category` and `::iterator_concept` lie - LWG3474 Nesting ``join_views`` is broken because of CTAD - added tests for an LWG issue that isn't resolved in the standard yet, but the previous code has workaround. - LWG3569 Inner iterator not default_initializable Reviewed By: #libc, var-const Spies: var-const, libcxx-commits Differential Revision: https://reviews.llvm.org/D123466
2022-04-21 13:08:34 +02:00
"`3500 <https://wg21.link/LWG3500>`__","``join_view::iterator::operator->()`` is bogus","February 2021","|Complete|","14.0","|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 12:22:25 +02:00
"`3502 <https://wg21.link/LWG3502>`__","``elements_view`` should not be allowed to return dangling reference","February 2021","","","|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-08 21:01:55 +02:00
"`3505 <https://wg21.link/LWG3505>`__","``split_view::outer-iterator::operator++`` misspecified","February 2021","","","|ranges|"
[libc++] [docs] [C++2b] Update status page with issues (and forgotten papers) adopted in November 2020 and February 2021 virtual meetings. Sources: * https://github.com/cplusplus/draft/pull/4380 (November 2020) * https://github.com/cplusplus/draft/pull/4523 (February 2021) * https://github.com/cplusplus/draft/issues?q=is%3Aissue+LWG+Motion
2021-03-01 10:31:29 +01:00
"","","","",""
[libc++][doc] Update the LWG issues. Updates the status pages with the LWG issues accepted in the Standard during the June 2021 plenary session. The LWG papers for this meeting have been added in D105103. Differential Revision: https://reviews.llvm.org/D106529
2021-07-22 08:04:48 +02:00
`2774 <https://wg21.link/LWG2774>`__,"``std::function`` construction vs assignment","June 2021","",""
[libc++] [NFC] Audit LWG issues for "Nothing To Do" and "Complete". Each "Nothing To Do" issue only changed nits in the English wording, not anything to do with the code. Each "Complete" issue was completed already, as far as I can tell. I tried to err on the side of caution: I didn't mark a few issues whose P/Rs were very invasive and would take time to verify, and I didn't mark a lot of issues involving features we haven't even started yet. Differential Revision: https://reviews.llvm.org/D117960
2022-01-22 12:26:27 -05:00
`2818 <https://wg21.link/LWG2818>`__,"``::std::`` everywhere rule needs tweaking","June 2021","|Nothing To Do|",""
[libc++][doc] Update the LWG issues. Updates the status pages with the LWG issues accepted in the Standard during the June 2021 plenary session. The LWG papers for this meeting have been added in D105103. Differential Revision: https://reviews.llvm.org/D106529
2021-07-22 08:04:48 +02:00
`2997 <https://wg21.link/LWG2997>`__,"LWG 491 and the specification of ``{forward_,}list::unique``","June 2021","",""
[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 12:22:25 +02:00
`3410 <https://wg21.link/LWG3410>`__,"``lexicographical_compare_three_way`` is overspecified","June 2021","","","|spaceship|"
[libc++][doc] Update the LWG issues. Updates the status pages with the LWG issues accepted in the Standard during the June 2021 plenary session. The LWG papers for this meeting have been added in D105103. Differential Revision: https://reviews.llvm.org/D106529
2021-07-22 08:04:48 +02:00
`3430 <https://wg21.link/LWG3430>`__,"``std::fstream`` & co. should be constructible from string_view","June 2021","",""
[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-08 21:01:55 +02:00
`3462 <https://wg21.link/LWG3462>`__,"§[formatter.requirements]: Formatter requirements forbid use of ``fc.arg()``","June 2021","","","|format|"
[libc++] [NFC] Audit LWG issues for "Nothing To Do" and "Complete". Each "Nothing To Do" issue only changed nits in the English wording, not anything to do with the code. Each "Complete" issue was completed already, as far as I can tell. I tried to err on the side of caution: I didn't mark a few issues whose P/Rs were very invasive and would take time to verify, and I didn't mark a lot of issues involving features we haven't even started yet. Differential Revision: https://reviews.llvm.org/D117960
2022-01-22 12:26:27 -05:00
`3481 <https://wg21.link/LWG3481>`__,"``viewable_range`` mishandles lvalue move-only views","June 2021","Superseded by `P2415R2 <https://wg21.link/P2415R2>`__","","|ranges|"
[libc++] Implement the resolutions of LWG3506 and LWG3522. Implement the changes in all language modes. LWG3506 "Missing allocator-extended constructors for priority_queue" makes the following changes: - New allocator-extended constructors for priority_queue. - New deduction guides targeting those constructors. LWG3522: "Missing requirement on InputIterator template parameter for priority_queue constructors". The iterator parameter should be constrained to actually be an iterator type. `priority_queue{1,2}` should be SFINAE-friendly ill-formed. Also, do a drive-by fix in the allocator-extended move constructor: there's no need to do a `make_heap` after moving from `__q.c` into our own `c`, because that container was already heapified when it was part of `__q`. [priqueue.cons.alloc] actually specifies the behavior and does *not* mention calling `make_heap`. I think this was just a copy-paste thinko. It dates back to the initial import of libc++. Differential Revision: https://reviews.llvm.org/D106824 Differential Revision: https://reviews.llvm.org/D106827
2021-03-02 00:23:21 -05:00
`3506 <https://wg21.link/LWG3506>`__,"Missing allocator-extended constructors for ``priority_queue``","June 2021","|Complete|","14.0"
[libcxx][ranges] add views::join adaptor object. added test coverage to join_view - added views::join adaptor object - added test for the adaptor object - fixed some join_view's tests. e.g iter_swap test - added some negative tests for join_view to test that operations do not exist when constraints aren't met - added tests that locks down issues that were already addressed in previous change - LWG3500 `join_view::iterator::operator->()` is bogus - LWG3313 `join_view::iterator::operator--` is incorrectly constrained - LWG3517 `join_view::iterator`'s `iter_swap` is underconstrained - P2328R1 join_view should join all views of ranges - fixed some issues in join_view and added tests - LWG3535 `join_view::iterator::iterator_category` and `::iterator_concept` lie - LWG3474 Nesting ``join_views`` is broken because of CTAD - added tests for an LWG issue that isn't resolved in the standard yet, but the previous code has workaround. - LWG3569 Inner iterator not default_initializable Reviewed By: #libc, var-const Spies: var-const, libcxx-commits Differential Revision: https://reviews.llvm.org/D123466
2022-04-21 13:08:34 +02:00
`3517 <https://wg21.link/LWG3517>`__,"``join_view::iterator``'s ``iter_swap`` is underconstrained","June 2021","|Complete|","14.0","|ranges|"
[libc++] [NFC] Audit LWG issues for "Nothing To Do" and "Complete". Each "Nothing To Do" issue only changed nits in the English wording, not anything to do with the code. Each "Complete" issue was completed already, as far as I can tell. I tried to err on the side of caution: I didn't mark a few issues whose P/Rs were very invasive and would take time to verify, and I didn't mark a lot of issues involving features we haven't even started yet. Differential Revision: https://reviews.llvm.org/D117960
2022-01-22 12:26:27 -05:00
`3518 <https://wg21.link/LWG3518>`__,"Exception requirements on char trait operations unclear","June 2021","|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 12:22:25 +02:00
`3519 <https://wg21.link/LWG3519>`__,"Incomplete synopses for ``<random>`` classes","June 2021","",""
[libc++] [NFC] Audit LWG issues for "Nothing To Do" and "Complete". Each "Nothing To Do" issue only changed nits in the English wording, not anything to do with the code. Each "Complete" issue was completed already, as far as I can tell. I tried to err on the side of caution: I didn't mark a few issues whose P/Rs were very invasive and would take time to verify, and I didn't mark a lot of issues involving features we haven't even started yet. Differential Revision: https://reviews.llvm.org/D117960
2022-01-22 12:26:27 -05:00
`3520 <https://wg21.link/LWG3520>`__,"``iter_move`` and ``iter_swap`` are inconsistent for ``transform_view::iterator``","June 2021","|Complete|","14.0","|ranges|"
`3521 <https://wg21.link/LWG3521>`__,"Overly strict requirements on ``qsort`` and ``bsearch``","June 2021","|Nothing To Do|",""
[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-08 21:01:55 +02:00
`3522 <https://wg21.link/LWG3522>`__,"Missing requirement on ``InputIterator`` template parameter for ``priority_queue`` constructors","June 2021","|Complete|","14.0","|ranges|"
`3523 <https://wg21.link/LWG3523>`__,"``iota_view::sentinel`` is not always ``iota_view``'s sentinel","June 2021","","","|ranges|"
[libc++][doc] Update the LWG issues. Updates the status pages with the LWG issues accepted in the Standard during the June 2021 plenary session. The LWG papers for this meeting have been added in D105103. Differential Revision: https://reviews.llvm.org/D106529
2021-07-22 08:04:48 +02:00
`3526 <https://wg21.link/LWG3526>`__,"Return types of ``uses_allocator_construction_args`` unspecified","June 2021","",""
`3527 <https://wg21.link/LWG3527>`__,"``uses_allocator_construction_args`` handles rvalue pairs of rvalue references incorrectly","June 2021","",""
`3528 <https://wg21.link/LWG3528>`__,"``make_from_tuple`` can perform (the equivalent of) a C-style cast","June 2021","",""
[libc++] [NFC] Audit LWG issues for "Nothing To Do" and "Complete". Each "Nothing To Do" issue only changed nits in the English wording, not anything to do with the code. Each "Complete" issue was completed already, as far as I can tell. I tried to err on the side of caution: I didn't mark a few issues whose P/Rs were very invasive and would take time to verify, and I didn't mark a lot of issues involving features we haven't even started yet. Differential Revision: https://reviews.llvm.org/D117960
2022-01-22 12:26:27 -05:00
`3529 <https://wg21.link/LWG3529>`__,"``priority_queue(first, last)`` should construct ``c`` with ``(first, last)``","June 2021","|Complete|","14.0"
[libc++][doc] Update the LWG issues. Updates the status pages with the LWG issues accepted in the Standard during the June 2021 plenary session. The LWG papers for this meeting have been added in D105103. Differential Revision: https://reviews.llvm.org/D106529
2021-07-22 08:04:48 +02:00
`3530 <https://wg21.link/LWG3530>`__,"``BUILTIN-PTR-MEOW`` should not opt the type out of syntactic checks","June 2021","",""
[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-08 21:01:55 +02:00
`3532 <https://wg21.link/LWG3532>`__,"``split_view<V, P>::inner-iterator<true>::operator++(int)`` should depend on ``Base``","June 2021","","","|ranges|"
[libc++] Fix LWG3533 "Make `base() const&` consistent..." Fixed in counted_iterator and transform_view::iterator. The LWG issue also affected elements_view::iterator, but we haven't implemented that one yet, and whoever does implement it will get the fix for free if they just follow the working draft's wording. Drive-by stop calling `.base()` on test iterators in the test, and improve the transform_view::iterator/sentinel tests. Differential Revision: https://reviews.llvm.org/D117329
2022-01-14 11:44:31 -05:00
`3533 <https://wg21.link/LWG3533>`__,"Make ``base() const &`` consistent across iterator wrappers that supports ``input_iterators``","June 2021","|Complete|","14.0","|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 12:22:25 +02:00
`3536 <https://wg21.link/LWG3536>`__,"Should ``chrono::from_stream()`` assign zero to duration for failure?","June 2021","","","|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-08 21:01:55 +02:00
`3539 <https://wg21.link/LWG3539>`__,"``format_to`` must not copy models of ``output_iterator<const charT&>``","June 2021","","","|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 14:43:43 +01:00
`3540 <https://wg21.link/LWG3540>`__,"§[format.arg] There should be no const in ``basic_format_arg(const T* p)``","June 2021","|Complete|","14.0","|format|"
[libc++] Mark LWG3541 as "Complete". NFC. Differential Revision: https://reviews.llvm.org/D117956
2022-01-22 13:06:05 -05:00
`3541 <https://wg21.link/LWG3541>`__,"``indirectly_readable_traits`` should be SFINAE-friendly for all types","June 2021","|Complete|","14.0","|ranges|"
[libc++][format] Mark LWG-issues as complete. Most of the code has been implemented using the eel.is draft. It seems some issues were inplemented but not marked as completed yet. Note the wording of LWG-3372 has been implemented, but has been changed in the current draft due to P2216, see D110494. Reviewed By: ldionne, #libc Differential Revision: https://reviews.llvm.org/D112363
2021-10-23 14:57:47 +02:00
`3542 <https://wg21.link/LWG3542>`__,"``basic_format_arg`` mishandles ``basic_string_view`` with custom traits","June 2021","|Complete|","14.0","|format|"
[libc++] [NFC] Audit LWG issues for "Nothing To Do" and "Complete". Each "Nothing To Do" issue only changed nits in the English wording, not anything to do with the code. Each "Complete" issue was completed already, as far as I can tell. I tried to err on the side of caution: I didn't mark a few issues whose P/Rs were very invasive and would take time to verify, and I didn't mark a lot of issues involving features we haven't even started yet. Differential Revision: https://reviews.llvm.org/D117960
2022-01-22 12:26:27 -05:00
`3543 <https://wg21.link/LWG3543>`__,"Definition of when ``counted_iterators`` refer to the same sequence isn't quite right","June 2021","|Nothing To Do|","","|ranges|"
`3544 <https://wg21.link/LWG3544>`__,"``format-arg-store::args`` is unintentionally not exposition-only","June 2021","|Complete|","14.0","|format|"
[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-08 21:01:55 +02:00
`3546 <https://wg21.link/LWG3546>`__,"``common_iterator``'s postfix-proxy is not quite right","June 2021","","","|ranges|"
[libc++] Make shared_ptr move unique_ptr's deleter Addresses LWG 3548 which mandates that when shared_ptr is being constructed from a unique_ptr, the unique_ptr's deleter should be moved and not copied. Reviewed By: #libc, philnik, EricWF Differential Revision: https://reviews.llvm.org/D119159
2022-03-18 11:36:25 -06:00
`3548 <https://wg21.link/LWG3548>`__,"``shared_ptr`` construction from ``unique_ptr`` should move (not copy) the deleter","June 2021","|Complete|","15.0"
[libc++] Implement LWG3549: view_interface need not inherit from view_base Implement LWG3549 by making `view_interface` not inherit from `view_base`. Types are still views if they have a public and unambiguous derivation from `view_interface`, so adjust the `enable_view` machinery as such to account for that. Differential Revision: https://reviews.llvm.org/D117714
2022-01-19 15:16:15 -05:00
`3549 <https://wg21.link/LWG3549>`__,"``view_interface`` is overspecified to derive from ``view_base``","June 2021","|Complete|","14.0","|ranges|"
[libc++] [NFC] Audit LWG issues for "Nothing To Do" and "Complete". Each "Nothing To Do" issue only changed nits in the English wording, not anything to do with the code. Each "Complete" issue was completed already, as far as I can tell. I tried to err on the side of caution: I didn't mark a few issues whose P/Rs were very invasive and would take time to verify, and I didn't mark a lot of issues involving features we haven't even started yet. Differential Revision: https://reviews.llvm.org/D117960
2022-01-22 12:26:27 -05:00
`3551 <https://wg21.link/LWG3551>`__,"``borrowed_{iterator,subrange}_t`` are overspecified","June 2021","|Nothing To Do|","","|ranges|"
[libc++][doc] Update the LWG issues. Updates the status pages with the LWG issues accepted in the Standard during the June 2021 plenary session. The LWG papers for this meeting have been added in D105103. Differential Revision: https://reviews.llvm.org/D106529
2021-07-22 08:04:48 +02:00
`3552 <https://wg21.link/LWG3552>`__,"Parallel specialized memory algorithms should require forward iterators","June 2021","",""
[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-08 21:01:55 +02:00
`3553 <https://wg21.link/LWG3553>`__,"Useless constraint in ``split_view::outer-iterator::value_type::begin()``","June 2021","","","|ranges|"
`3555 <https://wg21.link/LWG3555>`__,"``{transform,elements}_view::iterator::iterator_concept`` should consider const-qualification of the underlying range","June 2021","","","|ranges|"
[libc++][doc] Update the LWG issues. Updates the status pages with the LWG issues accepted in the Standard during the June 2021 plenary session. The LWG papers for this meeting have been added in D105103. Differential Revision: https://reviews.llvm.org/D106529
2021-07-22 08:04:48 +02:00
"","","","",""
[libc++] [NFC] Audit LWG issues for "Nothing To Do" and "Complete". Each "Nothing To Do" issue only changed nits in the English wording, not anything to do with the code. Each "Complete" issue was completed already, as far as I can tell. I tried to err on the side of caution: I didn't mark a few issues whose P/Rs were very invasive and would take time to verify, and I didn't mark a lot of issues involving features we haven't even started yet. Differential Revision: https://reviews.llvm.org/D117960
2022-01-22 12:26:27 -05:00
`2191 <https://wg21.link/LWG2191>`__,"Incorrect specification of ``match_results(match_results&&)``","October 2021","|Nothing To Do|",""
[libc++][doc] Update paper status. Update the status with the approved papers and LWG-issues in the October 2021 plenary. Reviewed By: #libc, ldionne Differential Revision: https://reviews.llvm.org/D111166
2021-10-05 18:18:16 +02:00
`2381 <https://wg21.link/LWG2381>`__,"Inconsistency in parsing floating point numbers","October 2021","",""
`2762 <https://wg21.link/LWG2762>`__,"``unique_ptr operator*()`` should be ``noexcept``","October 2021","",""
`3121 <https://wg21.link/LWG3121>`__,"``tuple`` constructor constraints for ``UTypes&&...`` overloads","October 2021","",""
[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 12:22:25 +02:00
`3123 <https://wg21.link/LWG3123>`__,"``duration`` constructor from representation shouldn't be effectively non-throwing","October 2021","","","|chrono|"
[libc++] [test] Fix LWG3146 "Excessive unwrapping in std::ref/cref" Drive-by constexprify the existing tests, too. Differential Revision: https://reviews.llvm.org/D117953
2022-01-22 12:18:51 -05:00
`3146 <https://wg21.link/LWG3146>`__,"Excessive unwrapping in ``std::ref/cref``","October 2021","|Complete|","14.0"
[libc++][doc] Update paper status. Update the status with the approved papers and LWG-issues in the October 2021 plenary. Reviewed By: #libc, ldionne Differential Revision: https://reviews.llvm.org/D111166
2021-10-05 18:18:16 +02:00
`3152 <https://wg21.link/LWG3152>`__,"``common_type`` and ``common_reference`` have flaws in common","October 2021","",""
Implement move_sentinel and C++20 move_iterator. Differential Revision: https://reviews.llvm.org/D117656
2022-01-19 06:26:52 -05:00
`3293 <https://wg21.link/LWG3293>`__,"``move_iterator operator+()`` has incorrect constraints","October 2021","|Complete|","15.0","|ranges|"
[libc++] [NFC] Audit LWG issues for "Nothing To Do" and "Complete". Each "Nothing To Do" issue only changed nits in the English wording, not anything to do with the code. Each "Complete" issue was completed already, as far as I can tell. I tried to err on the side of caution: I didn't mark a few issues whose P/Rs were very invasive and would take time to verify, and I didn't mark a lot of issues involving features we haven't even started yet. Differential Revision: https://reviews.llvm.org/D117960
2022-01-22 12:26:27 -05:00
`3361 <https://wg21.link/LWG3361>`__,"``safe_range<SomeRange&>`` case","October 2021","|Nothing To Do|","","|ranges|"
[libc++] [ranges] Implement std::ranges::distance This includes an experimental workaround for LWG3664 "LWG3392 broke std::ranges::distance(a, a+3)", but the workaround may be incomplete, I'm not sure. This should be re-audited when LWG3664 is actually adopted, to see if we need to change anything about our implementation. See also https://github.com/microsoft/STL/pull/2500 Differential Revision: https://reviews.llvm.org/D117940
2022-01-21 15:51:46 -05:00
`3392 <https://wg21.link/LWG3392>`__,"``ranges::distance()`` cannot be used on a move-only iterator with a sized sentinel","October 2021","|Complete|","14.0","|ranges|"
[libc++][ranges] Implement `views::drop`. The view itself has been implemented previously -- this patch only adds the ability to pipe it. Also finishes the implementation of [P1739](https://wg21.link/p1739) and [LWG3407](https://wg21.link/lwg3407). Differential Revision: https://reviews.llvm.org/D125156
2022-05-10 09:29:39 -07:00
`3407 <https://wg21.link/LWG3407>`__,"Some problems with the wording changes of P1739R4","October 2021","|Complete|","15.0","|ranges|"
[libc++] Fix LWG3422 "Issues of seed_seq's constructors" https://cplusplus.github.io/LWG/issue3422 Also add a static_assert to check the "Mandates:" on the iterator-pair constructor. Oddly, the `InputIterator` parameter itself is merely preconditioned, not constrained, to satisfy the input iterator requirements. Also drive-by rename `init` to `__init`. Differential Revision: https://reviews.llvm.org/D117962
2022-01-22 15:13:13 -05:00
`3422 <https://wg21.link/LWG3422>`__,"Issues of ``seed_seq``'s constructors","October 2021","|Complete|","14.0"
[libc++] [ranges] Fix LWG3470 "convertible-to-non-slicing seems to reject valid case" Differential Revision: https://reviews.llvm.org/D117941
2022-01-21 23:29:41 -05:00
`3470 <https://wg21.link/LWG3470>`__,"``convertible-to-non-slicing`` seems to reject valid case","October 2021","|Complete|","14.0","|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-08 21:01:55 +02:00
`3480 <https://wg21.link/LWG3480>`__,"``directory_iterator`` and ``recursive_directory_iterator`` are not C++20 ranges","October 2021","|Complete|","14.0","|ranges|"
[libc++][doc] Update paper status. Update the status with the approved papers and LWG-issues in the October 2021 plenary. Reviewed By: #libc, ldionne Differential Revision: https://reviews.llvm.org/D111166
2021-10-05 18:18:16 +02:00
`3498 <https://wg21.link/LWG3498>`__,"Inconsistent ``noexcept``-specifiers for ``basic_syncbuf``","October 2021","",""
[libcxx][ranges] add views::join adaptor object. added test coverage to join_view - added views::join adaptor object - added test for the adaptor object - fixed some join_view's tests. e.g iter_swap test - added some negative tests for join_view to test that operations do not exist when constraints aren't met - added tests that locks down issues that were already addressed in previous change - LWG3500 `join_view::iterator::operator->()` is bogus - LWG3313 `join_view::iterator::operator--` is incorrectly constrained - LWG3517 `join_view::iterator`'s `iter_swap` is underconstrained - P2328R1 join_view should join all views of ranges - fixed some issues in join_view and added tests - LWG3535 `join_view::iterator::iterator_category` and `::iterator_concept` lie - LWG3474 Nesting ``join_views`` is broken because of CTAD - added tests for an LWG issue that isn't resolved in the standard yet, but the previous code has workaround. - LWG3569 Inner iterator not default_initializable Reviewed By: #libc, var-const Spies: var-const, libcxx-commits Differential Revision: https://reviews.llvm.org/D123466
2022-04-21 13:08:34 +02:00
`3535 <https://wg21.link/LWG3535>`__,"``join_view::iterator::iterator_category`` and ``::iterator_concept`` lie","October 2021","|Complete|","15.0","|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 12:22:25 +02:00
`3554 <https://wg21.link/LWG3554>`__,"``chrono::parse`` needs ``const charT*`` and ``basic_string_view<charT>`` overloads","October 2021","","","|chrono|"
[libc++] Fix LWG3557 "static_cast expression in convertible_to has the wrong operand" https://cplusplus.github.io/LWG/issue3557 I think the code change is unobservable, so we could just close this as "Nothing To Do" instead; but it seems appropriate to follow the Standard's wording here as closely as possible. Differential Revision: https://reviews.llvm.org/D117964
2022-01-22 15:29:18 -05:00
`3557 <https://wg21.link/LWG3557>`__,"The ``static_cast`` expression in ``convertible_to`` has the wrong operand","October 2021","|Complete|","14.0"
[libc++] [NFC] Audit LWG issues for "Nothing To Do" and "Complete". Each "Nothing To Do" issue only changed nits in the English wording, not anything to do with the code. Each "Complete" issue was completed already, as far as I can tell. I tried to err on the side of caution: I didn't mark a few issues whose P/Rs were very invasive and would take time to verify, and I didn't mark a lot of issues involving features we haven't even started yet. Differential Revision: https://reviews.llvm.org/D117960
2022-01-22 12:26:27 -05:00
`3559 <https://wg21.link/LWG3559>`__,"Semantic requirements of ``sized_range`` is circular","October 2021","|Nothing To Do|","","|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-08 21:01:55 +02:00
`3560 <https://wg21.link/LWG3560>`__,"``ranges::equal`` and ``ranges::is_permutation`` should short-circuit for ``sized_ranges``","October 2021","","","|ranges|"
[libc++][doc] Update paper status. Update the status with the approved papers and LWG-issues in the October 2021 plenary. Reviewed By: #libc, ldionne Differential Revision: https://reviews.llvm.org/D111166
2021-10-05 18:18:16 +02:00
`3561 <https://wg21.link/LWG3561>`__,"Issue with internal counter in ``discard_block_engine``","October 2021","",""
[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-08 21:01:55 +02:00
`3563 <https://wg21.link/LWG3563>`__,"``keys_view`` example is broken","October 2021","","","|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 12:22:25 +02:00
`3566 <https://wg21.link/LWG3566>`__,"Constraint recursion for ``operator<=>(optional<T>, U)``","October 2021","","","|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-08 21:01:55 +02:00
`3567 <https://wg21.link/LWG3567>`__,"Formatting move-only iterators take two","October 2021","","","|format|"
implement `std::views::istream` implement `std::ranges::basic_istream_view` and `std::views::istream`. Although the view itself is constexpr, the constructor argument is a base class std::istream where its ctor/dtor are not constexpr. So no tests are performed in constexpr Differential Revision: https://reviews.llvm.org/D133317
2022-09-05 16:45:47 +01:00
`3568 <https://wg21.link/LWG3568>`__,"``basic_istream_view`` needs to initialize ``value_``","October 2021","|Complete|","16.0","|ranges|"
[libc++][doc] Update paper status. Update the status with the approved papers and LWG-issues in the October 2021 plenary. Reviewed By: #libc, ldionne Differential Revision: https://reviews.llvm.org/D111166
2021-10-05 18:18:16 +02:00
`3570 <https://wg21.link/LWG3570>`__,"``basic_osyncstream::emit`` should be an unformatted output function","October 2021","",""
`3571 <https://wg21.link/LWG3571>`__,"``flush_emit`` should set ``badbit`` if the ``emit`` call fails","October 2021","",""
[libc++] [NFC] Audit LWG issues for "Nothing To Do" and "Complete". Each "Nothing To Do" issue only changed nits in the English wording, not anything to do with the code. Each "Complete" issue was completed already, as far as I can tell. I tried to err on the side of caution: I didn't mark a few issues whose P/Rs were very invasive and would take time to verify, and I didn't mark a lot of issues involving features we haven't even started yet. Differential Revision: https://reviews.llvm.org/D117960
2022-01-22 12:26:27 -05:00
`3572 <https://wg21.link/LWG3572>`__,"``copyable-box`` should be fully ``constexpr``","October 2021","|Complete|","14.0","|ranges|"
[libc++][NFC] Mark LWG3573 as complete Mark LWG3573 as complete. It involves a change in wording around when `basic_string_view`'s constructor for iterator/sentinel can throw. The current implementation is not marked conditionally `noexcept`, so there is nothing to do here. Add a test that binds this behavior to verify the constructor is not marked `noexcept(true)` when `end - begin` throws. Reviewed By: ldionne, Mordante, #libc Differential Revision: https://reviews.llvm.org/D111925
2021-10-19 14:18:36 -04:00
`3573 <https://wg21.link/LWG3573>`__,"Missing Throws element for ``basic_string_view(It begin, End end)``","October 2021","|Complete|","14.0"
[libc++] Fix bugs in common_iterator; add test coverage. Differential Revision: https://reviews.llvm.org/D117400
2022-01-15 13:29:26 -05:00
`3574 <https://wg21.link/LWG3574>`__,"``common_iterator`` should be completely ``constexpr``-able","October 2021","|Complete|","14.0","|ranges|"
[libc++] [NFC] Audit LWG issues for "Nothing To Do" and "Complete". Each "Nothing To Do" issue only changed nits in the English wording, not anything to do with the code. Each "Complete" issue was completed already, as far as I can tell. I tried to err on the side of caution: I didn't mark a few issues whose P/Rs were very invasive and would take time to verify, and I didn't mark a lot of issues involving features we haven't even started yet. Differential Revision: https://reviews.llvm.org/D117960
2022-01-22 12:26:27 -05:00
`3580 <https://wg21.link/LWG3580>`__,"``iota_view``'s ``iterator``'s binary ``operator+`` should be improved","October 2021","|Complete|","14.0","|ranges|"
`3581 <https://wg21.link/LWG3581>`__,"The range constructor makes ``basic_string_view`` not trivially move constructible","October 2021","|Complete|","14.0","|ranges|"
[libc++][doc] Update paper status. Update the status with the approved papers and LWG-issues in the October 2021 plenary. Reviewed By: #libc, ldionne Differential Revision: https://reviews.llvm.org/D111166
2021-10-05 18:18:16 +02:00
`3585 <https://wg21.link/LWG3585>`__,"``variant`` converting assignment with immovable alternative","October 2021","",""
[libc++] Fix LWG3589 "The const lvalue reference overload of get for subrange..." https://cplusplus.github.io/LWG/issue3589 Differential Revision: https://reviews.llvm.org/D117961
2022-01-22 14:33:12 -05:00
`3589 <https://wg21.link/LWG3589>`__,"The ``const`` lvalue reference overload of ``get`` for ``subrange`` does not constrain ``I`` to be ``copyable`` when ``N == 0``","October 2021","|Complete|","14.0","|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-08 21:01:55 +02:00
`3590 <https://wg21.link/LWG3590>`__,"``split_view::base() const &`` is overconstrained","October 2021","","","|ranges|"
`3591 <https://wg21.link/LWG3591>`__,"``lazy_split_view<input_view>::inner-iterator::base() &&`` invalidates outer iterators","October 2021","","","|ranges|"
`3592 <https://wg21.link/LWG3592>`__,"``lazy_split_view`` needs to check the simpleness of Pattern","October 2021","","","|ranges|"
`3593 <https://wg21.link/LWG3593>`__,"Several iterators' ``base() const &`` and ``lazy_split_view::outer-iterator::value_type::end()`` missing ``noexcept``","October 2021","","","|ranges|"
[libc++] Fix bugs in common_iterator; add test coverage. Differential Revision: https://reviews.llvm.org/D117400
2022-01-15 13:29:26 -05:00
`3595 <https://wg21.link/LWG3595>`__,"Exposition-only classes proxy and postfix-proxy for ``common_iterator`` should be fully ``constexpr``","October 2021","|Complete|","14.0","|ranges|"
[libc++][doc] Update paper status. Update the status with the approved papers and LWG-issues in the October 2021 plenary. Reviewed By: #libc, ldionne Differential Revision: https://reviews.llvm.org/D111166
2021-10-05 18:18:16 +02:00
"","","","",""
[libc++] Add LWG-issues from february 2022 plenary meeting Reviewed By: ldionne, Quuxplusone, Mordante, #libc Spies: libcxx-commits Differential Revision: https://reviews.llvm.org/D119443
2022-02-10 18:08:36 +01:00
"`3088 <https://wg21.link/LWG3088>`__","``forward_list::merge`` behaviour unclear when passed ``*this``","February 2022","",""
"`3471 <https://wg21.link/LWG3471>`__","``polymorphic_allocator::allocate`` does not satisfy ``Cpp17Allocator`` requirements","February 2022","",""
"`3525 <https://wg21.link/LWG3525>`__","``uses_allocator_construction_args`` fails to handle types convertible to ``pair``","February 2022","",""
"`3598 <https://wg21.link/LWG3598>`__","``system_category().default_error_condition(0)`` is underspecified","February 2022","",""
"`3601 <https://wg21.link/LWG3601>`__","common_iterator's postfix-proxy needs ``indirectly_readable`` ","February 2022","","","|ranges|"
"`3607 <https://wg21.link/LWG3607>`__","``contiguous_iterator`` should not be allowed to have custom ``iter_move`` and ``iter_swap`` behavior","February 2022","|Nothing to do|","","|ranges|"
"`3610 <https://wg21.link/LWG3610>`__","``iota_view::size`` sometimes rejects integer-class types","February 2022","","","|ranges|"
"`3612 <https://wg21.link/LWG3612>`__","Inconsistent pointer alignment in ``std::format`` ","February 2022","|Complete|","14.0","|format|"
"`3616 <https://wg21.link/LWG3616>`__","LWG 3498 seems to miss the non-member ``swap`` for ``basic_syncbuf`` ","February 2022","",""
"`3618 <https://wg21.link/LWG3618>`__","Unnecessary ``iter_move`` for ``transform_view::iterator`` ","February 2022","","","|ranges|"
"`3619 <https://wg21.link/LWG3619>`__","Specification of ``vformat_to`` contains ill-formed ``formatted_size`` calls","February 2022","|Nothing to do|","","|format|"
[libc++] Removes __cpp_lib_monadic_optional. P0798R8 "Monadic operations for std::optional" has been implemented, so this LWG issue can be adopted. During review it was discovered another paper bumped the macro. The part affecting optional of this paper is done, the variant isn't. The status page is updated to reflect the current state. Implements - LWG 3621 Remove feature-test macro __cpp_lib_monadic_optional Updates status of - P2231R1 Missing constexpr in std::optional and std::variant Reviewed By: #libc, philnik, ldionne Differential Revision: https://reviews.llvm.org/D125813
2022-05-17 19:15:18 +02:00
"`3621 <https://wg21.link/LWG3621>`__","Remove feature-test macro ``__cpp_lib_monadic_optional`` ","February 2022","|Complete|","15.0"
[libc++] [NFC] Fix a typo in Cxx2bIssues.csv Differential Revision: https://reviews.llvm.org/D119694
2022-02-14 10:57:45 -05:00
"`3632 <https://wg21.link/LWG3632>`__","``unique_ptr`` ""Mandates: This constructor is not selected by class template argument deduction""","February 2022","|Nothing to do|",""
[libc++] Add LWG-issues from february 2022 plenary meeting Reviewed By: ldionne, Quuxplusone, Mordante, #libc Spies: libcxx-commits Differential Revision: https://reviews.llvm.org/D119443
2022-02-10 18:08:36 +01:00
"`3643 <https://wg21.link/LWG3643>`__","Missing ``constexpr`` in ``std::counted_iterator`` ","February 2022","",""
[libc++][format] LWG-3648 format should not print bool with 'c' Reviewed By: #libc, ldionne Differential Revision: https://reviews.llvm.org/D119350
2022-02-09 17:36:12 +01:00
"`3648 <https://wg21.link/LWG3648>`__","``format`` should not print ``bool`` with ``'c'`` ","February 2022","|Complete|","15.0","|format|"
[libc++] Add LWG-issues from february 2022 plenary meeting Reviewed By: ldionne, Quuxplusone, Mordante, #libc Spies: libcxx-commits Differential Revision: https://reviews.llvm.org/D119443
2022-02-10 18:08:36 +01:00
"`3649 <https://wg21.link/LWG3649>`__","[fund.ts.v2] Reinstate and bump ``__cpp_lib_experimental_memory_resource`` feature test macro","February 2022","",""
"`3650 <https://wg21.link/LWG3650>`__","Are ``std::basic_string`` 's ``iterator`` and ``const_iterator`` constexpr iterators?","February 2022","|Nothing to do|",""
[libc++][format] LWG-3654 basic_format_context::arg(size_t) should be noexcept Reviewed By: #libc, ldionne Differential Revision: https://reviews.llvm.org/D119349
2022-02-09 17:36:12 +01:00
"`3654 <https://wg21.link/LWG3654>`__","``basic_format_context::arg(size_t)`` should be ``noexcept`` ","February 2022","|Complete|","15.0","|format|"
[libc++] Add LWG-issues from february 2022 plenary meeting Reviewed By: ldionne, Quuxplusone, Mordante, #libc Spies: libcxx-commits Differential Revision: https://reviews.llvm.org/D119443
2022-02-10 18:08:36 +01:00
"`3657 <https://wg21.link/LWG3657>`__","``std::hash<std::filesystem::path>`` is not enabled","February 2022","",""
"`3660 <https://wg21.link/LWG3660>`__","``iterator_traits<common_iterator>::pointer`` should conform to §[iterator.traits]","February 2022","|Complete|","14.0"
[libc++] [LWG3656] Update the return type of std::bit_width. Fixes LWG3656, "Inconsistent bit operations returning a count". https://cplusplus.github.io/LWG/issue3656 The fix has been approved for C++23 and left to vendors' discretion in C++20 (but it sounds like everyone's on the same page that of course it should be DR'ed back to C++20 too). Differential Revision: https://reviews.llvm.org/D120444
2022-02-23 20:08:28 -05:00
"`3661 <https://wg21.link/LWG3661>`__","``constinit atomic<shared_ptr<T>> a(nullptr);`` should work","February 2022","",""
[libc++] Add LWG-issues from february 2022 plenary meeting Reviewed By: ldionne, Quuxplusone, Mordante, #libc Spies: libcxx-commits Differential Revision: https://reviews.llvm.org/D119443
2022-02-10 18:08:36 +01:00
"","","","",""
[libc++][doc] Updates status documents. Adds the papers and LWG issues voted in during the July 2022 plenary. Note the updating of the project based statuses is left to the active contributors of these projects. Reviewed By: #libc, huixie90, philnik Differential Revision: https://reviews.llvm.org/D130595
2022-07-26 19:37:06 +02:00
"`3564 <https://wg21.link/LWG3564>`__","``transform_view::iterator<true>::value_type`` and ``iterator_category`` should use ``const F&``","July 2022","","","|ranges|"
"`3617 <https://wg21.link/LWG3617>`__","``function``/``packaged_task`` deduction guides and deducing ``this``","July 2022","",""
"`3656 <https://wg21.link/LWG3656>`__","Inconsistent bit operations returning a count","July 2022","|Complete|","15.0",""
"`3659 <https://wg21.link/LWG3659>`__","Consider ``ATOMIC_FLAG_INIT`` undeprecation","July 2022","|Complete|","15.0"
"`3670 <https://wg21.link/LWG3670>`__","``Cpp17InputIterators`` don't have integer-class difference types","July 2022","","","|ranges|"
"`3671 <https://wg21.link/LWG3671>`__","``atomic_fetch_xor`` missing from ``stdatomic.h``","July 2022","",""
"`3672 <https://wg21.link/LWG3672>`__","``common_iterator::operator->()`` should return by value","July 2022","","","|ranges|"
"`3683 <https://wg21.link/LWG3683>`__","``operator==`` for ``polymorphic_allocator`` cannot deduce template argument in common cases","July 2022","",""
"`3687 <https://wg21.link/LWG3687>`__","``expected<cv void, E>`` move constructor should move","July 2022","",""
"`3692 <https://wg21.link/LWG3692>`__","``zip_view::iterator``'s ``operator<=>`` is overconstrained","July 2022","","","|spaceship|"
"`3701 <https://wg21.link/LWG3701>`__","Make ``formatter<remove_cvref_t<const charT[N]>, charT>`` requirement explicit","July 2022","","","|format|"
"`3702 <https://wg21.link/LWG3702>`__","Should ``zip_transform_view::iterator`` remove ``operator<``","July 2022","",""
"`3703 <https://wg21.link/LWG3703>`__","Missing requirements for ``expected<T, E>`` requires ``is_void<T>``","July 2022","",""
"`3704 <https://wg21.link/LWG3704>`__","LWG 2059 added overloads that might be ill-formed for sets","July 2022","",""
[libc++] Enable hash only for the correct types Also implement LWG3705. Fixes https://github.com/llvm/llvm-project/issues/55823 Reviewed By: ldionne, #libc Spies: libcxx-commits Differential Revision: https://reviews.llvm.org/D132338
2022-08-22 02:59:09 +02:00
"`3705 <https://wg21.link/LWG3705>`__","Hashability shouldn't depend on basic_string's allocator","July 2022","|Complete|","16.0"
[libc++][doc] Updates status documents. Adds the papers and LWG issues voted in during the July 2022 plenary. Note the updating of the project based statuses is left to the active contributors of these projects. Reviewed By: #libc, huixie90, philnik Differential Revision: https://reviews.llvm.org/D130595
2022-07-26 19:37:06 +02:00
"`3707 <https://wg21.link/LWG3707>`__","chunk_view::outer-iterator::value_type::size should return unsigned type","July 2022","","","|ranges|"
"`3708 <https://wg21.link/LWG3708>`__","``take_while_view::sentinel``'s conversion constructor should move","July 2022","","","|ranges|"
"`3709 <https://wg21.link/LWG3709>`__","LWG-3703 was underly ambitious","July 2022","",""
"`3710 <https://wg21.link/LWG3710>`__","The ``end`` of ``chunk_view`` for input ranges can be ``const``","July 2022","","","|ranges|"
"`3711 <https://wg21.link/LWG3711>`__","Missing preconditions for slide_view constructor","July 2022","","","|ranges|"
"`3712 <https://wg21.link/LWG3712>`__","``chunk_view`` and ``slide_view`` should not be ``default_initializable``","July 2022","","","|ranges|"
"`3713 <https://wg21.link/LWG3713>`__","Sorted with respect to comparator (only)","July 2022","",""
"`3715 <https://wg21.link/LWG3715>`__","``view_interface::empty`` is overconstrained","July 2022","",""
"`3719 <https://wg21.link/LWG3719>`__","Directory iterators should be usable with default sentinel","July 2022","",""
[libc++][format] Allows width arg-id with value 0. Implements: - LWG3721 Allow an arg-id with a value of zero for width in std-format-spec Reviewed By: ldionne, #libc Differential Revision: https://reviews.llvm.org/D130649
2022-07-27 19:17:08 +02:00
"`3721 <https://wg21.link/LWG3721>`__","Allow an ``arg-id`` with a value of zero for ``width`` in ``std-format-spec``","July 2022","|Complete|","16.0","|format|"
[libc++][doc] Updates status documents. Adds the papers and LWG issues voted in during the July 2022 plenary. Note the updating of the project based statuses is left to the active contributors of these projects. Reviewed By: #libc, huixie90, philnik Differential Revision: https://reviews.llvm.org/D130595
2022-07-26 19:37:06 +02:00
"`3724 <https://wg21.link/LWG3724>`__","``decay-copy`` should be constrained","July 2022","|Complete|","14.0"
"","","","",""
[libc++] Fix ADL for `make_error_{code,condition}` Implement LWG 3629, by making lookup for make_error_code and make_error_condition only consider names found by ADL. This is achieved by adding a block scope using-declaration for a function that will be found by unqualified lookup, preventing unqualified lookup from continuing to enclosing scopes (the class scope, then enclosing namespaces). The function named by the using declaration is not viable, so overload resolution must select a candidate found by ADL. This fixes https://github.com/llvm/llvm-project/issues/57614 Differential Revision: https://reviews.llvm.org/D134943
2022-09-30 09:22:01 -04:00
"`3629 <https://wg21.link/LWG3629>`__","``make_error_code`` and ``make_error_condition`` are customization points","Not voted in","|Complete|","16.0",""
[libc++][format] Use forwarding references. This implements a not accepted LWG issue. Not doing so would require integral types to use the handle class instead of being directly stored in the basic_format_arg. The previous code used `std::forward` in places where it wasn't required by the Standard. These are now removed. Implements: - P2418R2 Add support for std::generator-like types to std::format - LWG 3631 basic_format_arg(T&&) should use remove_cvref_t<T> throughout Reviewed By: ldionne, #libc Differential Revision: https://reviews.llvm.org/D127570
2021-10-05 19:25:37 +02:00
"`3631 <https://wg21.link/LWG3631>`__","``basic_format_arg(T&&)`` should use ``remove_cvref_t<T>`` throughout","Not voted in","|Complete|","15.0",""
[libc++] Fix ADL for `make_error_{code,condition}` Implement LWG 3629, by making lookup for make_error_code and make_error_condition only consider names found by ADL. This is achieved by adding a block scope using-declaration for a function that will be found by unqualified lookup, preventing unqualified lookup from continuing to enclosing scopes (the class scope, then enclosing namespaces). The function named by the using declaration is not viable, so overload resolution must select a candidate found by ADL. This fixes https://github.com/llvm/llvm-project/issues/57614 Differential Revision: https://reviews.llvm.org/D134943
2022-09-30 09:22:01 -04:00
"`3645 <https://wg21.link/LWG3645>`__","``resize_and_overwrite`` is overspecified to call its callback with lvalues","Not voted in","|Complete|","14.0",""
[libc++][format] Implements formattable concept. This concept is introduced in P2286, but was implemented in libc++ before. This implementation was used in the library internally. This implementation lacked the resolution of LWG3636. The original formatter had a non-const member function that wasn't trivial to make a const member. The recent parser improvements made this member a const member in preparation of LWG3636. Note LWG3636 isn't voted in. Its status is Ready. P2286's concept has been written as-if LWG3636 is accepted and refers to that LWG issue. Updates some tests make format a const member function and removes a tests that's mainly a duplicate of the formattable concept test. Implements - LWG3636 formatter<T>::format should be const-qualified Implements parts of - P2286R8 Formatting Ranges Reviewed By: ldionne, #libc Differential Revision: https://reviews.llvm.org/D134110
2022-09-17 13:34:00 +02:00
"`3636 <https://wg21.link/LWG3636>`__","``formatter<T>::format`` should be ``const``-qualified","Not voted in","|Complete|","16.0",""
[libc++] Mark LWG3541 as "Complete". NFC. Differential Revision: https://reviews.llvm.org/D117956
2022-01-22 13:06:05 -05:00
"","","","",""
Reference in New Issue Copy Permalink