[libcxx-commits] [PATCH] D136657: [libc++][ranges][NFC] Revamp the Ranges status page

[Louis Dionne via Phabricator via libcxx-commits]

ldionne added inline comments.


================
Comment at: libcxx/docs/Status/RangesIssues.csv:1
-"Number","Name","Status","First released version"
-`P0896R4 <https://wg21.link/P0896R4>`__,<ranges>,|Complete|,15.0
-`P1035R7 <https://wg21.link/P1035R7>`__,Input Range Adaptors,,
-`P1207R4 <https://wg21.link/P1207R4>`__,Movability Of Single-Pass Iterators,|Complete|,15.0
-`P1243R4 <https://wg21.link/P1243R4>`__,Rangify New Algorithms,|Complete|,15.0
-`P1248R1 <https://wg21.link/P1248R1>`__,Fixing Relations,|Complete|,13.0
-`P1252R2 <https://wg21.link/P1252R2>`__,Ranges Design Cleanup,|Complete|,15.0
-`P1391R4 <https://wg21.link/P1391R4>`__,Range Constructor For string_view,|Complete|,14.0
-`P1456R1 <https://wg21.link/P1456R1>`__,Move-Only Views,|Complete|,15.0
-`P1474R1 <https://wg21.link/P1474R1>`__,Helpful Pointers For contiguous_iterator,|Complete|,15.0
-`P1522R1 <https://wg21.link/P1522R1>`__,Iterator Difference Type And Integer Overflow,|Complete|,15.0
-`P1523R1 <https://wg21.link/P1523R1>`__,Views And Size Types,|Complete|,15.0
-`P1638R1 <https://wg21.link/P1638R1>`__,basic_istream_view::iterator Should Not Be Copyable,,
-`P1716R3 <https://wg21.link/P1716R3>`__,Range Comparison Algorithms Are Over-Constrained,|Complete|,15.0
-`P1739R4 <https://wg21.link/P1739R4>`__,Avoiding Template Bloat For Ranges,|Complete|,15.0
-`P1862R1 <https://wg21.link/P1862R1>`__,Range Adaptors For Non-Copyable Iterators,,
-`P1870R1 <https://wg21.link/P1870R1>`__,forwarding-range<T> is too subtle,|Complete|,15.0
-`P1871R1 <https://wg21.link/P1871R1>`__,Concept traits should be named after concepts,|Complete|,14.0
-`P1878R1 <https://wg21.link/P1878R1>`__,Constraining Readable Types,|Complete|,15.0
-`P1970R2 <https://wg21.link/P1970R2>`__,Consistency for size() functions: Add ranges::ssize,|Complete|,15.0
-`P1983R0 <https://wg21.link/P1983R0>`__,"Wording for GB301, US296, US292, US291, and US283",|Complete|,15.0
-`P1994R1 <https://wg21.link/P1994R1>`__,elements_view Needs Its Own sentinel,,
-`P2091R0 <https://wg21.link/P2091R0>`__,Fixing Issues With Range Access CPOs,|Complete|,15.0
-`P2106R0 <https://wg21.link/P2106R0>`__,Alternative wording for GB315 and GB316,|Complete|,15.0
-
-`P2325R3 <https://wg21.link/P2325R3>`__,Views should not be required to be default constructible ,,
-`P2328R1 <https://wg21.link/P2328R1>`__,join_view should join all views of ranges,|Complete|,14.0
-`P2210R2 <https://wg21.link/P2210R2>`__,Superior String Splitting,,
-`P2281R1 <https://wg21.link/P2281R1>`__,Clarifying range adaptor objects,|Complete|,14.0
-`P2367R0 <https://wg21.link/P2367R0>`__,Remove misuses of list-initialization from Clause 24,,
-
-`P2415 <https://wg21.link/P2415>`__,"What is a ``view``",|Complete|,14.0
-`P2432 <https://wg21.link/P2432>`__,"Fix ``istream_view``",,
+"Number","Name","Status"
+"`3173 <https://wg21.link/LWG3173>`__","Enable CTAD for ``ref-view``\ ",✅
----------------
Do we need that separate page? Can't we track those using the normal C++20/C++23 issues page?


================
Comment at: libcxx/docs/Status/RangesPapers.csv:1
+"Number","Name","Status"
+"`P0896R4 <https://wg21.link/P0896R4>`__","The One Ranges Proposal",✅
----------------
Same here -- why don't we track that from the C++20/C++23 papers page instead?


Repository:
  rG LLVM Github Monorepo

CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D136657/new/

https://reviews.llvm.org/D136657