SG16 will hold a meeting *tomorrow*, Wednesday, September 10th, at 19:30
UTC (timezone conversion
<https://www.timeanddate.com/worldclock/converter.html?iso=20250910T193000&p1=1440&p2=tz_pdt&p3=tz_mdt&p4=tz_cdt&p5=tz_edt&p6=tz_cest>).

If you need a .ics file to import into your calendar, you can download
it here
<https://documents.isocpp.org/remote.php/dav/public-calendars/R7imgS2LJD9xfeWN/94A3D3A0-70B9-4847-935F-9453DB2BB216.ics?export>.

The agenda is:

  * P3681R0: char_traits: Stop the bleeding! <https://wg21.link/p3681r0>
  * P3672R0: On Windows, Systems APIs, Text Encodings, and Pragmatism
    <https://wg21.link/p3672r0>.

*P3681R0* is Corentin's attempt to dissuade the continued appearance of
std::char_traits in new standard library features and comes to us
following discussions of P3655 (std::zstring_view)
<https://wg21.link/p3655>. SG16 discussed P3655R0 during the 2025-04-23
SG16 meeting
<https://wiki.edg.com/bin/view/Wg21telecons2025/SG16Teleconference2025-04-23>
where we took the following poll.

    *Poll 1: P3655R0: No objection to use of std::char_traits for
    consistency and compatibility with std::string_view.*

    **

       * Attendees: 8 (no abstentions)
       *
        SF
         F
         N
         A
         SA
        7
         1
         0
         0
         0

      * Strong consensus.

Corentin was not present for that meeting, so this paper does not
represent a change of opinion from him, but rather a request to
reconsider that poll and to perhaps establish a policy related to
std::char_traits for future work. The paper explicitly addresses the
possibility of custom char trait types and how such existing use with
std::basic_string would impact convertibility to std::zstring_view.

*P3672R0* is an opinion paper that discusses encoding expectations on
different platforms, the consequences of command line arguments and file
paths that are not well-formed text, the degree to which we should care
about such content, and the impact such complexity can, and should, have
on standard library features and interfaces. Thoughts on these issues
has implications for P3474R0 (std::arguments)
<https://wg21.link/p3474r0>; a paper we last discussed during the
2025-04-09 SG16 meeting
<https://wiki.edg.com/bin/view/Wg21telecons2025/SG16Teleconference2025-04-09> and
which is currently awaiting a new revision
<https://github.com/cplusplus/papers/issues/2128#issuecomment-2791081002>.

Tom.