-
Notifications
You must be signed in to change notification settings - Fork 1
CWG2843 Undated reference to Unicode makes C++ a moving target #1736
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
Comments
Also forwarded to EWG on request of the EWG chair. |
SG16 discussed this issue during the January 10th, 2024 SG16 meeting. The following polls were taken:
Further discussion of this issue is planned for the 2024-02-07 SG16 meeting. I'll provide a more detailed summary of the SG16 consensus following that meeting. |
SG16 discussed this issue during the February 7th, 2024 SG16 meeting. The following polls were taken:
Further discussion regarding changes needed for Unicode 15.1.0 was scheduled for the 2024-07-21 SG16 meeting. I'll provide a detailed summary of the SG16 consensus when the minutes for that meeting are published. |
SG16 concluded its review of this issue during its 2024-02-21 meeting. No additional polls were taken. The SG16 consensus is as follows:
Steve Downey has volunteered to draft updates for annex E. SG16 review is complete. This issue is now solely in CWG's capable hands. |
Correction, this issue awaits review from EWG and LWG. The updates that Steve has volunteered to draft are still pending as well, but those correspond to non-normative content. |
EWG discussed this issue during the Monday AM session in Tokyo. The following poll was taken: Forward SG16's suggestions (allow implementation defined version, with a mininum version of 15.1.0) to CWG for inclusion in C++ as a DR against C++23.
Result: Consensus |
Adding "needs-revision" while waiting for the Annex E update. No need for CWG to context-switch to this paper more often than necessary. |
Clause 2 [intro.refs] paragraph 1.10 uses an undated reference for the Unicode standard, meaning that a published (and otherwise frozen) standard for C++ (e.g. C++23) will implicitly refer to a new revision of the Unicode standard the moment such is issued.
This situation might be considered strictly worse than the lack of support for certain scripts or languages, which can be rectified by updating the reference to Unicode in the next revision of the C++ standard, as is regularly done with any other missing language feature deemed worth addressing.
CWG solicits advice from SG16 and LWG on handling this matter.
CWG2843
The text was updated successfully, but these errors were encountered: