According to @aaron.ballman this was marked Tentatively Ready as of 2022-07-07.
D129362 implemented the C counterpart.
Details
- Reviewers
ldionne cor3ntin aaron.ballman erichkeane philnik Mordante - Group Reviewers
Restricted Project - Commits
- rG1544d1f9fdb1: [libc++] Undeprecate ATOMIC_FLAG_INIT (LWG3659)
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Please wait until the LWG issue has been accepted.
libcxx/docs/ReleaseNotes.rst | ||
---|---|---|
50 | We currently don't release-note LWG issues. I don't know if it would make sense to do so. We only started release-noting papers in this release cycle. | |
libcxx/docs/Status/Cxx2bIssues.csv | ||
159 | This wasn't accepted in February 2022. You also forgot to update the number. |
To be clear on the status: LWG has accepted this as tentatively ready, but there is a short window for people to object to that status which would pull the issue back into needing committee discussion. Given the subject matter, it'd be quite surprising if anyone did so, and so this is expected to go into C++23 (and should be treated as DR against C++20).
I'm not certain of libc++'s schedule, but I'm hoping to land the C changes in Clang shortly so that they make it into Clang 15 in an effort to limit user confusion (Clang 14 shipped with the diagnostic enabled).
Thanks for the additional information. The libc++ policy is not to implement LWG-issue before they are voted in at a plenary, but we make exceptions when needed.
When this gets accepted in the next plenary we definitely should ship this in LLVM 15, however that doesn't mean we need land it before the branching happens, there still time afterwards see
https://discourse.llvm.org/t/llvm-15-0-0-release-schedule/63495/7 and
https://discourse.llvm.org/t/llvm-15-0-0-release-schedule/63495/9
Based on @aaron.ballman's comment I'm in favour to land this after the review comments have been addressed. In the unexpected case it doesn't get voted is we can revert the change.
@ldionne how do you feel about landing this before it's voted in at the next plenary?
libcxx/docs/ReleaseNotes.rst | ||
---|---|---|
50 | I've no strong opinion whether or not to add it. I don't think we need to list all LWG issues, since some of the are not really "user visible", but this one is. | |
libcxx/docs/Status/Cxx2bIssues.csv | ||
159 | The issues on this page are group by the plenary where they were accepted. Please move this to the bottom of the proper place for the July 2022 plenary. | |
159 | I would like to see an update the note for P0883 with information regarding this LWG issue. |
libcxx/docs/Status/Cxx2bIssues.csv | ||
---|---|---|
159 | Done. Added the note to the P0883's line on the C++20 status page. Hopefully that's what you intended. |
I am fine with landing this even though the LWG issue hasn't been voted in officially. We normally don't do that too often, however I think this is a good case to make an exception since this is pretty user-visible.
We currently don't release-note LWG issues. I don't know if it would make sense to do so. We only started release-noting papers in this release cycle.