Date: Tue, 13 Dec 2022 17:27:47 -0500
SG16 will hold a telecon on Wednesday, December 14th, at 19:30 UTC
(timezone conversion
<https://www.timeanddate.com/worldclock/converter.html?iso=20221214T193000&p1=1440&p2=tz_pst&p3=tz_mst&p4=tz_cst&p5=tz_est&p6=tz_cet>).
*This message will also serve as your friendly reminder that this
meeting is taking place tomorrow. **I'm sorry for, again, publishing an
agenda so very late. *
The agenda follows.
* D2675R1: LWG3780: The Paper (format's width estimation is too
approximate and not forward compatible)
<https://isocpp.org/files/papers/D2675R1.pdf>
o LWG #3780: format's width estimation is too approximate and not
forward compatible <https://cplusplus.github.io/LWG/issue3780>
o FR-007-012 22.14.2.2 [format.string.std] codepoints with width 2
<https://github.com/cplusplus/nbballot/issues/409>
* FR-020-014 5.3 [lex.charset] Replace "translation character set" by
"Unicode" <https://github.com/cplusplus/nbballot/issues/422>
We started discussing P2675R0 <https://wg21.link/p2675r0> (LWG3780: The
Paper (format's width estimation is too approximate and not forward
compatible)) during our 2022-11-30 telecon (for which I still haven't
gotten minutes published; I will strive to have it out before we meet
tomorrow). The paper is intended to resolve LWG #3780
<https://cplusplus.github.io/LWG/issue3780> and FR-007-012
<https://github.com/cplusplus/nbballot/issues/409>. It seeks to replace
the explicit list of code point ranges in [format.string.std]p12
<https://eel.is/c++draft/format.string.std#12> with wording that derives
substantially the same set of code points using Unicode database
properties. Corentin posted the draft revision from the agenda to a
thread on the SG16 mailing list
<https://lists.isocpp.org/sg16/2022/11/3603.php> shortly after our last
discussion.
Candidate Poll 3.1: P2675R0: Forward to LEWG as the recommended
resolution of FR-007-012 [amended to ...].
Candidate Poll 3.2: P2675R0: Forward to LEWG for C++26 [amended to ...].
Candidate Poll 3.3: Recommend to LEWG that FR-007-012 be rejected.
FR-020-014 <https://github.com/cplusplus/nbballot/issues/422> raises
concerns that were discussed as part of the reviews of P2314
<https://wg21.link/p2314> and P2297 <https://wg21.link/p2297> during the
2021-03-24 SG16 meeting
<https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2021.md#march-24th-2021>.
The comment does not appear to present new information. If we choose to
accept, a paper will need to be quickly produced.
Candidate poll 4.1: Recommend to CWG that FR-020-014 be accepted.
Candidate poll 4.2: Recommend to CWG that FR-020-014 be rejected.
Tom.
(timezone conversion
<https://www.timeanddate.com/worldclock/converter.html?iso=20221214T193000&p1=1440&p2=tz_pst&p3=tz_mst&p4=tz_cst&p5=tz_est&p6=tz_cet>).
*This message will also serve as your friendly reminder that this
meeting is taking place tomorrow. **I'm sorry for, again, publishing an
agenda so very late. *
The agenda follows.
* D2675R1: LWG3780: The Paper (format's width estimation is too
approximate and not forward compatible)
<https://isocpp.org/files/papers/D2675R1.pdf>
o LWG #3780: format's width estimation is too approximate and not
forward compatible <https://cplusplus.github.io/LWG/issue3780>
o FR-007-012 22.14.2.2 [format.string.std] codepoints with width 2
<https://github.com/cplusplus/nbballot/issues/409>
* FR-020-014 5.3 [lex.charset] Replace "translation character set" by
"Unicode" <https://github.com/cplusplus/nbballot/issues/422>
We started discussing P2675R0 <https://wg21.link/p2675r0> (LWG3780: The
Paper (format's width estimation is too approximate and not forward
compatible)) during our 2022-11-30 telecon (for which I still haven't
gotten minutes published; I will strive to have it out before we meet
tomorrow). The paper is intended to resolve LWG #3780
<https://cplusplus.github.io/LWG/issue3780> and FR-007-012
<https://github.com/cplusplus/nbballot/issues/409>. It seeks to replace
the explicit list of code point ranges in [format.string.std]p12
<https://eel.is/c++draft/format.string.std#12> with wording that derives
substantially the same set of code points using Unicode database
properties. Corentin posted the draft revision from the agenda to a
thread on the SG16 mailing list
<https://lists.isocpp.org/sg16/2022/11/3603.php> shortly after our last
discussion.
Candidate Poll 3.1: P2675R0: Forward to LEWG as the recommended
resolution of FR-007-012 [amended to ...].
Candidate Poll 3.2: P2675R0: Forward to LEWG for C++26 [amended to ...].
Candidate Poll 3.3: Recommend to LEWG that FR-007-012 be rejected.
FR-020-014 <https://github.com/cplusplus/nbballot/issues/422> raises
concerns that were discussed as part of the reviews of P2314
<https://wg21.link/p2314> and P2297 <https://wg21.link/p2297> during the
2021-03-24 SG16 meeting
<https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2021.md#march-24th-2021>.
The comment does not appear to present new information. If we choose to
accept, a paper will need to be quickly produced.
Candidate poll 4.1: Recommend to CWG that FR-020-014 be accepted.
Candidate poll 4.2: Recommend to CWG that FR-020-014 be rejected.
Tom.
Received on 2022-12-13 22:27:50