Hi Tom and other Unicoders,
Can we review an updated revision of P2286 (https://brevzin.github.io/cpp_proposals/2286_fmt_ranges/p2286r4.html) during the upcoming meeting since there is still chance that it can target C++23? This revision addresses the SG16 feedback, particularly around escaping (https://brevzin.github.io/cpp_proposals/2286_fmt_ranges/p2286r4.html#escaping-behavior). I think it's way more important and time sensitive than LWG issues related to fill.
The linked paper is labeled as P2286R4, but has not yet been
submitted for a mailing. Please refrain from using "P" designators
with papers that might be changed prior to submission; I suspect
this revision should currently be labeled as D2286R4. If the
intent is that any subsequent changes will be added to an R5, then
please submit this revision as is so that it can be linked from
the paper submission system.
On Fri, Dec 10, 2021 at 2:53 PM Tom Honermann via SG16 <firstname.lastname@example.org> wrote:
SG16 will hold a telecon on Wednesday, December 15th at 19:30 UTC (timezone conversion).
The agenda is:
- P2361R4: Unevaluated strings
- Poll forwarding to EWG for C++23.
- P1854R2: Conversion to literal encoding should not lead to loss of meaning
- Discuss and poll forwarding to EWG for C++23.
- LWG3639: Handling of fill character width is underspecified in std::format
LWG3576: Clarifying fill character in std::format
- Pending an updated proposed resolution from Tom, review and poll forwarding to LWG.
We last reviewed P2361R3 and D1854R2 at our 2021-11-17 telecon and Corentin has dutifully updated both papers to address the review feedback. Per a message thread on the SG16 mailing list, there appears to be good agreement that P2316R4 is ready to be forwarded to EWG, so we'll provide an opportunity for discussion and then poll forwarding it. Similar expectations are present for P1854R2, though we don't have explicit confirmation of that.
For the LWG issues, I intend to provide an updated proposed resolution that addresses feedback from our 2021-12-01 telecon (sorry, this link won't work until I get the minutes published; today or tomorrow). I'll send the update to the SG16 mailing list when ready.
SG16 mailing list