[libcxx-commits] [PATCH] D145127: [libc++][doc] Mark LWG-3720 as "Nothing to do"

Mark de Wever via Phabricator via libcxx-commits libcxx-commits at lists.llvm.org
Fri Mar 3 08:51:03 PST 2023


Mordante added inline comments.


================
Comment at: libcxx/docs/Status/Cxx2bIssues.csv:253
 "`3664 <https://wg21.link/LWG3664>`__","`LWG 3392 <https://wg21.link/LWG3392>`__ ``broke std::ranges::distance(a, a+3)``","February 2023","","","|ranges|"
-"`3720 <https://wg21.link/LWG3720>`__","Restrict the valid types of ``arg-id`` for width and precision in ``std-format-spec``","February 2023","","","|format|"
+"`3720 <https://wg21.link/LWG3720>`__","Restrict the valid types of ``arg-id`` for width and precision in ``std-format-spec``","February 2023","Nothing to do","","|format|"
 "`3756 <https://wg21.link/LWG3756>`__","Is the ``std::atomic_flag`` class signal-safe?","February 2023","","",""
----------------
fsb4000 wrote:
> Mordante wrote:
> > Actually I disagree with this statement, see D144326
> Ok.
> 
> I thought `__i128` and `__u128` are supported as libc++ extension.
They are, but the LWG issue's wording explicitly mentions `standard signed or unsigned integer`. My original wording didn't contain the word `standard`, but during LWG review that was added. Therefore I wanted to remove 128-bit support here.


Repository:
  rG LLVM Github Monorepo

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

https://reviews.llvm.org/D145127



More information about the libcxx-commits mailing list