Closed wg21bot closed 1 year ago
@tahonermann you get first crack at this. Send it back to us when it's ready.
SG16 reviewed this issue during its 2022-11-02 telecon. The following poll was taken:
See the SG16 review notes for US 38-098 for additional details.
This is ready for LEWG review.
FR-005-134: Aggressive escaping
US-38-098: Escaping for debugging and logging
2022-11-07 15:15 to 17:00 UTC-10 Kona Library Evolution Minutes
Champion: Victor Zverovich (in-person)
Chair: Nevin Liber & Fabio Fracassi
Minute Taker: Steve Downey
POLL: We agree with the direction of the proposed SG16 recommendation for US-38-098 & FR-005-134.
Strongly Favor | Weakly Favor | Neutral | Weakly Against | Strongly Against |
---|---|---|---|---|
9 | 7 | 0 | 0 | 0 |
Outcome: Unanimous consent
Take a Library Evolution electronic poll to send the proposed SG16 recommendation for US-38-098 & FR-005-134 to Library for C++23, classified as B2 - Improvement.
I need a paper with the proposed resolution for Library Evolution electronic polling.
SG16 reviewed P2713R0 (Escaping improvements in std::format) during its [2022-11-30 telecon](). The following poll was taken.
P2713R1 implements the SG16 requested wording changes.
@brycelelbach, the needs-paper
label should now be removed; this issue is again ready for LEWG consideration.
"needs-paper" removed.
This has a paper now, P2713 https://github.com/cplusplus/papers/issues/1418.
Labeling has-paper
.
LWG saw this via telecom ahead of Issaquah
https://wiki.edg.com/bin/view/Wg21telecons2023/P2713-20230201
See details in the paper issue.
Accepted with modifications; se P2713R1 for details.
The intent of "escaped strings" is unclear and unsuited to many spoken languages
As it stands, this features escapes ● Invalid code unit sequences ● Non printable characters ● All combining marks and other grapheme extenders ● Whitespaces using different techniques ● escape \ and " It is not clear that all these behaviours should be regrouped in the same facility. In particular, escaping all combining codepoints is not suitable for many languages, especially Korean.
Please consider either: ● Not escaping combining codepoints which are part of a grapheme cluster. Removing this feature and replace it by a set of facility performing each of these operations in a future C++ standard