Thank you to everyone that attended today.

The slides presented will be published with the meeting summary. In the meantime, you can find them here if interested. Links included in the slides are below:

Unicode Message Format Working Group (MFWG):

Draft specification (available in the spec folder of the develop branch).

Unicode Source Ad Hoc Group (SCWG):

Changes to UAX #9 included in Unicode 15: L2/22-172.
Changes to UAX #31 included in Unicode 15: L2/22-179.

Backward compatibility impact from P1949:

SG16 issue #79: Migration challenges following P1949 changes to identifier syntax.
Clang bug report #54732: Clang 14 rejects certain Unicode characters in identifiers that are accepted by Clang 13 and the C++ Standard.
L2/22-102: A survey of non-XID identifier usage in program text

Tom.

On 9/13/22 5:15 PM, Tom Honermann via SG16 wrote:

This is your friendly reminder that this meeting is taking place tomorrow.

Tom.

On 9/10/22 9:47 AM, Tom Honermann via SG16 wrote:

SG16 will hold a telecon on Wednesday, September 14th, at 19:30 UTC (timezone conversion).

The agenda is:

Report on the on-going interactions between WG21 and the Unicode Consortium.

Report on the backward compatibility impact of P1949 (C++ Identifier Syntax using Unicode Standard Annex 31).

Continued discussion of P2626R0: charN_t incremental adoption: Casting pointers of UTF character types.

SG16 has previously engaged with the Unicode Message Format Working Group (MFWG) (in our March 11th, 2020 telecon) and the Unicode Source Code Ad Hoc Group (SCAHG) (in our May 25th, 2022 telecon with Robin Leroy). Peter and Tom have continued engaging with these groups. Tom will report on their activities (Peter is not expected to be available for this meeting).

Implementation of P1949 in Clang (as a DR unconditionally applied to older language modes) prompted some users to report substantial impact to projects that previously enjoyed use of mathematical symbols in identifiers. Tom will report on some specifics of the impact, discussion between Clang implementors, and on-going work by the SCAHG that may provide a solution in the future. Further discussion should focus on guidance that we may want to offer to implementors.

Pending Corentin's availability, we'll continue discussion of P2626R0 from our August 24th, 2022 telecon.

Tom.