On 10/9/24 2:53 AM, Corentin Jabot wrote:
>
>
> On Tue, Oct 8, 2024 at 11:28 PM Tom Honermann via SG16
> <sg16_at_[hidden]> wrote:
>
> SG16 will hold a meeting *tomorrow*, Wednesday, October 9th, at
> 19:30 UTC (timezone conversion
> <https://www.timeanddate.com/worldclock/converter.html?iso=20241009T193000&p1=1440&p2=tz_pdt&p3=tz_mdt&p4=tz_cdt&p5=tz_edt&p6=tz_cest>).
>
> The agenda follows.
>
> * P3094R3: std::basic_fixed_string <https://wg21.link/p3094r3>
> * P3045R1: Quantities and units library <https://wg21.link/p3045r1>
> * P3258R0: Formatting of charN_t <https://wg21.link/p3258r0>
>
> SG16 has not previously reviewed P3094, but did discuss a
> fixed_string type in the context of a predecessor paper, P2980R0
> (A motivation, scope, and plan for a physical quantities and units
> library) <https://wg21.link/p2980r0> during its 2023-11-29 meeting
> <https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2023.md#november-29th-2023>.
> Since we're fairly familiar with the subject matter, so I'll ask
> Mateusz to provide a brief overview and we'll move on to
> discussion of any concerns. SG16 has not previously polled this
> paper or its predecessor; the LEWG chair will be looking for SG16
> to bless this paper even if we don't see SG16 specific concerns to
> ensure this paper is ready for progress in Wrocław.
>
> What are the SG-16-relevant topics of discussion for this paper?
> I guess we should discuss nuking char_traits?

It isn't clear to me that there are any SG16 specific concerns and I
won't be disappointed if we don't find any! :)

There has been a fair amount of discussion happening on the LEWG mailing
list (that I haven't found time to read yet). I'm not sure what all has
been brought up in those discussions.

Tom.

> SG16 reviewed previous revisions of P3045 during its 2023-11-29
> meeting
> <https://github.com/sg16-unicode/sg16-meetings/blob/master/README-2023.md#november-29th-2023>
> and 2024-01-24 meeting
> <https://github.com/sg16-unicode/sg16-meetings/blob/master/README.md#january-24th-2024>.
> Previous discussion concerned which encodings to support and
> representation for symbols, particularly those not represented in
> the basic character sets. Mateusz can provide an overview of the
> changes and any relevant design changes that have been made. The
> LEWG chair will also be looking for SG16 to determine if there are
> any lingering SG16 concerns that would prevent this paper
> progressing at Wrocław.
>
> P3258R0 comes to us courtesy of Corentin and seeks to achieve what
> most people expect to be trivial but which we have always known to
> be impossible; provide formatting and I/O support for text in
> char/N/_t, sort of, as limited by the characters representable in
> the ordinary and wide literal encodings. Corentin to provide an
> overview and frown while the rest of us quibble about transcoding
> details and locale encodings and, probably, reluctantly, conclude
> that the behavior Corentin has proposed is how things should be.
>
> Tom.
>
> --
> SG16 mailing list
> SG16_at_[hidden]
> https://lists.isocpp.org/mailman/listinfo.cgi/sg16
>