[libcxx-commits] [PATCH] D111458: [libc++][doc] Use issue labels.

[Mark de Wever via Phabricator via libcxx-commits]

Mordante marked 8 inline comments as done.
Mordante added a comment.

I created a followup marking the issues @Quuxplusone identified and several more in D111935 <https://reviews.llvm.org/D111935>.
.



================
Comment at: libcxx/docs/Status/Cxx20Issues.csv:210-211
+"`3250 <https://wg21.link/LWG3250>`__","``std::format``\ : ``#``\  (alternate form) for NaN and inf","Prague","","","|format|"
 "`3251 <https://wg21.link/LWG3251>`__","Are ``std::format``\  alignment specifiers applied to string arguments?","Prague","",""
 "`3252 <https://wg21.link/LWG3252>`__","Parse locale's aware modifiers for commands are not consistent with POSIX spec","Prague","",""
 "`3254 <https://wg21.link/LWG3254>`__","Strike ``stop_token``\ 's ``operator!=``\ ","Prague","",""
----------------
Quuxplusone wrote:
> Should these say `|format|`?
No it should be `|chrono|`.


================
Comment at: libcxx/docs/Status/Cxx2bIssues.csv:116
+`3535 <https://wg21.link/LWG3535>`__,"``join_view::iterator::iterator_category`` and ``::iterator_concept`` lie","October 2021","","","|ranges|"
 `3554 <https://wg21.link/LWG3554>`__,"``chrono::parse`` needs ``const charT*`` and ``basic_string_view<charT>`` overloads","October 2021","",""
 `3557 <https://wg21.link/LWG3557>`__,"The ``static_cast`` expression in ``convertible_to`` has the wrong operand","October 2021","",""
----------------
Mordante wrote:
> Quuxplusone wrote:
> > Should this say `|chrono| |format|`? (Incidentally, I'd prefer this alphabetical order over your `|format| |chrono|`; but not a blocker.)
> As mentioned in the description I'd like to mark additional papers in a separate commit. Then I also want to look for spaceship related issues to be marked. I prefer to get the initial part in first to avoid getting merge conflicts (I'm sure I already have some).
> 
> I put `|format| |chrono|` in this order since it's logical to me, but I agree alphabetic order is better. I'll fix that prior to committing; one regex replacement and I'm done ;-)
This is only `|chrono|`. The `<chrono>` header has its own `parse` function that's unrelated to `<format>`.


Repository:
  rG LLVM Github Monorepo

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

https://reviews.llvm.org/D111458