-
Notifications
You must be signed in to change notification settings - Fork 18
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
P1885 R12 Naming Text Encodings to Demystify Them #634
Comments
SG16 reviewed P1885R0 in Belfast and approved forwarding to LEWG for C++23. Removing the SG16 label. SG16 minutes are available at: |
P1885R1 Naming Text Encodings to Demystify Them (Corentin Jabot) |
SG16 will revisit this paper in Prague. Re-adding the SG16 label. |
SG16 in Prague: Approved with modification. Minutes are at http://wiki.edg.com/bin/view/Wg21prague/SG16D1885R2. SG16 will review future revisions of this paper again, but supports the direction. D1885R2: We want to support non-IANA registered encodings provided by the implementation.
Consensus? Yes D1885R2: We want to support non-IANA registered encodings provided by the programmer.
Consensus? No D1885R2: Forward to LEWG/EWG with support for this direction knowing that we will revisit a future revision.
Consensus? Yes Adding the |
P1885R2 Naming Text Encodings to Demystify Them (Corentin Jabot) |
P1885R3 Naming Text Encodings to Demystify Them (Corentin Jabot) |
2022-05 Library Evolution Electronic Poll OutcomesPOLL: Return [P1885R10] Naming Text Encodings to Demystify Them to Library Working Group for C++23, classified as an addition ([P0592R4] bucket 3 item).
Consensus in favor. |
This missed 23 moving to 26. |
LWG reviewed and approved....several times... https://wiki.edg.com/bin/view/Wg21telecons2023/P1885-20230308 Put P1885R12 into c++26 |F|A|N| |
P1885R11 Naming Text Encodings to Demystify Them (Corentin Jabot, Peter Brett) |
P1885R12 Naming Text Encodings to Demystify Them (Corentin Jabot, Peter Brett) |
P1885R0 Naming Text Encodings to Demystify Them (Corentin Jabot)
The text was updated successfully, but these errors were encountered: