Date: Sat, 11 Dec 2021 14:00:34 -0800
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.
Cheers,
Victor
On Fri, Dec 10, 2021 at 2:53 PM Tom Honermann via SG16 <
sg16_at_[hidden]> wrote:
> SG16 will hold a telecon on Wednesday, December 15th at 19:30 UTC (timezone
> conversion
> <https://www.timeanddate.com/worldclock/converter.html?iso=20211215T193000&p1=1440&p2=tz_pst&p3=tz_mst&p4=tz_cst&p5=tz_est&p6=tz_cet>
> ).
>
> The agenda is:
>
> - P2361R4: Unevaluated strings <https://wg21.link/p2361r4>
> - Poll forwarding to EWG for C++23.
> - P1854R2: Conversion to literal encoding should not lead to loss
> of meaning <https://wg21.link/p1854r2>
> - Discuss and poll forwarding to EWG for C++23.
> - LWG3639: Handling of fill character width is underspecified in
> std::format <https://wg21.link/lwg3639>
> LWG3576: Clarifying fill character in std::format
> <https://wg21.link/lwg3576>
> - 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
> <https://github.com/sg16-unicode/sg16-meetings#november-17th-2021> and
> Corentin has dutifully updated both papers to address the review feedback.
> Per a message thread on the SG16 mailing list
> <https://lists.isocpp.org/sg16/2021/12/2888.php>, 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
> <https://github.com/sg16-unicode/sg16-meetings#december-1st-2021> (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.
>
> Tom.
> --
> SG16 mailing list
> SG16_at_[hidden]
> https://lists.isocpp.org/mailman/listinfo.cgi/sg16
>
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.
Cheers,
Victor
On Fri, Dec 10, 2021 at 2:53 PM Tom Honermann via SG16 <
sg16_at_[hidden]> wrote:
> SG16 will hold a telecon on Wednesday, December 15th at 19:30 UTC (timezone
> conversion
> <https://www.timeanddate.com/worldclock/converter.html?iso=20211215T193000&p1=1440&p2=tz_pst&p3=tz_mst&p4=tz_cst&p5=tz_est&p6=tz_cet>
> ).
>
> The agenda is:
>
> - P2361R4: Unevaluated strings <https://wg21.link/p2361r4>
> - Poll forwarding to EWG for C++23.
> - P1854R2: Conversion to literal encoding should not lead to loss
> of meaning <https://wg21.link/p1854r2>
> - Discuss and poll forwarding to EWG for C++23.
> - LWG3639: Handling of fill character width is underspecified in
> std::format <https://wg21.link/lwg3639>
> LWG3576: Clarifying fill character in std::format
> <https://wg21.link/lwg3576>
> - 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
> <https://github.com/sg16-unicode/sg16-meetings#november-17th-2021> and
> Corentin has dutifully updated both papers to address the review feedback.
> Per a message thread on the SG16 mailing list
> <https://lists.isocpp.org/sg16/2021/12/2888.php>, 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
> <https://github.com/sg16-unicode/sg16-meetings#december-1st-2021> (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.
>
> Tom.
> --
> SG16 mailing list
> SG16_at_[hidden]
> https://lists.isocpp.org/mailman/listinfo.cgi/sg16
>
Received on 2021-12-11 16:00:48