Date: Sat, 11 Dec 2021 18:23:50 -0500
> On Dec 11, 2021, at 5:00 PM, Victor Zverovich <victor.zverovich_at_[hidden]> wrote:
>
>
> 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.
I agree, the LWG issues can be addressed any time during the C++23 cycle. We’ll therefore discuss the updated P2286 next week after Corentin’s papers. Thanks to you and Barry for turning out a new revision so quickly!
Tom.
>
> 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).
>>
>> 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.
>>
>> Tom.
>>
>> --
>> SG16 mailing list
>> SG16_at_[hidden]
>> https://lists.isocpp.org/mailman/listinfo.cgi/sg16
>
>
> 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.
I agree, the LWG issues can be addressed any time during the C++23 cycle. We’ll therefore discuss the updated P2286 next week after Corentin’s papers. Thanks to you and Barry for turning out a new revision so quickly!
Tom.
>
> 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).
>>
>> 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.
>>
>> Tom.
>>
>> --
>> SG16 mailing list
>> SG16_at_[hidden]
>> https://lists.isocpp.org/mailman/listinfo.cgi/sg16
Received on 2021-12-11 17:23:53