My rough notes for this meeting are available on the WG21 wiki here
<https://wiki.edg.com/bin/view/Wg21telecons2025/SG16Teleconference2025-12-10>.

The P3688 GH issue <https://github.com/cplusplus/papers/issues/2318> has
been updated to reflect the poll that was taken.

I expect to schedule further discussion of this paper for the 2025-01-14
SG16 meeting. Jan published the P3688R5 <https://wg21.link/p3688r5>
revision a few days after we met. I have not thoroughly reviewed the new
revision, but a brief look suggests that it addresses feedback raised
during the last meeting. I encourage others to review both the posted
meeting summary and the new revision and to raise any concerns with the
author before we review again.

Happy New Year!

Tom.

On 12/9/25 12:10 AM, Tom Honermann via SG16 wrote:
>
> SG16 will hold a meeting *tomorrow*, Wednesday, December 10th, at
> 19:30 UTC (timezone conversion
> <https://www.timeanddate.com/worldclock/converter.html?iso=20251210T193000&p1=1440&p2=tz_pst&p3=tz_mst&p4=tz_cst&p5=tz_est&p6=tz_cet>).
>
> The agenda is:
>
> * P3688R4: ASCII character utilities <https://wg21.link/p3688r4>.
>
> This will be the last SG16 meeting for this calendar year. We'll
> resume meetings in the new year starting January 14th.
>
> We started discussing *P3688R4* during the last SG16 meeting on
> 2024-11-19
> <https://wiki.edg.com/bin/view/Wg21telecons2025/SG16Teleconference2025-11-19>,
> but quickly ran out of time. That brief discussion touched on function
> names, but little else. We'll continue discussion and if all goes
> well, poll forwarding the paper to LEWG. Jan and Corentin, please note
> Hubert's follow up message to the SG16 mailing list
> <http://lists.isocpp.org/sg16/2025/12/4648.php> (Hubert, I have yet to
> follow up on your WG14 liaison question, but it is on my todo list).
>
> If there isn't much discussion, then this will be a short meeting. I'm
> not putting any other items on the agenda so that we don't end up in
> the situation of a discussion that doesn't reach closure before the
> holiday break and the inevitable memory flush that will come with it.
>
> Tom.
>
>