-
Notifications
You must be signed in to change notification settings - Fork 11.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[libc++] Add a release note about C++03 being frozen after LLVM 21 #95894
Conversation
@llvm/pr-subscribers-libcxx Author: Nikolas Klauser (philnik777) ChangesFull diff: https://github.com/llvm/llvm-project/pull/95894.diff 1 Files Affected:
diff --git a/libcxx/docs/ReleaseNotes/19.rst b/libcxx/docs/ReleaseNotes/19.rst
index 71de10abb6eaa..cffe40cec2618 100644
--- a/libcxx/docs/ReleaseNotes/19.rst
+++ b/libcxx/docs/ReleaseNotes/19.rst
@@ -77,6 +77,8 @@ Improvements and New Features
Deprecations and Removals
-------------------------
+- The status of the C++03 implementation will be frozen. From now on only bug fixes will be back-ported to C++03.
+
- The C++20 synchronization library (``<barrier>``, ``<latch>``, ``atomic::wait``, etc.) has been deprecated
in language modes prior to C++20. If you are using these features prior to C++20, please update to ``-std=c++20``.
In LLVM 20, the C++20 synchronization library will be removed entirely in language modes prior to C++20.
@@ -133,8 +135,8 @@ LLVM 20
LLVM 21
~~~~~~~
-TODO
+- Libc++ will no longer back-port non-critical bug fixes to C++03.
ABI Affecting Changes
---------------------
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for doing this! I'd like a bit more verbosity though, I think this change is important enough that we need to do a good job at communicating it.
Could you add a 21.rst with the related news? |
545fd2a
to
d4ef64f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM with the reformulation!
In particular, I think it's important not to commit to a particular implementation of this proposal. The steps laid out in https://discourse.llvm.org/t/rfc-freezing-c-03-headers-in-libc/77319/55 are nice, but we don't know if it's actually going to work exactly that way.
Also, I think we must avoid promising that we're going to freeze the headers completely, since that may not be achievable.
Co-authored-by: Louis Dionne <[email protected]>
…lvm#95894) Co-authored-by: Louis Dionne <[email protected]>
…lvm#95894) Co-authored-by: Louis Dionne <[email protected]>
…95894) Summary: Co-authored-by: Louis Dionne <[email protected]> Test Plan: Reviewers: Subscribers: Tasks: Tags: Differential Revision: https://phabricator.intern.facebook.com/D60251018
No description provided.