[libcxx-commits] [libcxx] [libc++][optional] LWG4497: `std::nullopt_t` should be comparable (PR #214975)

A. Jiang via libcxx-commits libcxx-commits at lists.llvm.org
Sun Aug 16 16:48:30 PDT 2026


================
@@ -17,3 +17,6 @@
 "`LWG4567 <https://wg21.link/LWG4567>`__","Feature test macro value for ``apply_result``, ``is_applicable``","2026-06 (Brno)","","","`#204455 <https://github.com/llvm/llvm-project/issues/204455>`__",""
 "`LWG4568 <https://wg21.link/LWG4568>`__","``std::execution::spawn_future`` is mishandling dependent senders","2026-06 (Brno)","","","`#204456 <https://github.com/llvm/llvm-project/issues/204456>`__",""
 "`LWG4579 <https://wg21.link/LWG4579>`__","``make-state<Rcvr>::state-type::complete`` uses ``Env`` which is not in scope","2026-06 (Brno)","","","`#204457 <https://github.com/llvm/llvm-project/issues/204457>`__",""
+"","","","","","",""
+"`LWG4612 <https://wg21.link/LWG4612>`__","Specify the details of ``std::nullopt_t``","Not Adopted Yet","|Complete|","24","",""
----------------
frederick-vs-ja wrote:

This is a bit more complicated then I thought, but still fine.

If LWG4612 is not yet adopted in the next meeting, we should be more careful when running the script, though.

https://github.com/llvm/llvm-project/pull/214975


More information about the libcxx-commits mailing list