P1949 C++ Identifier Syntax using Unicode Standard Annex 31

[wg21bot]

P1949R0 C++ Identifier Syntax using Unicode Standard Annex 31 (Steve Downey)

[tahonermann]

SG16 in Belfast: Needs revision.

SG16 reviewed a draft of this paper in Belfast during our discussions of NL029. The author was present. We're looking forward to a revision for C++23 that addresses C compatibility, implementation experience, and that has wording.

SG16 minutes are available with the minutes for the discussion of NL029 at:

• http://wiki.edg.com/bin/view/Wg21belfast/SG16NBNL029

[wg21bot]

P1949R1 C++ Identifier Syntax using Unicode Standard Annex 31 (Steve Downey, Zach Laine, Tom Honermann, Peter Bindels)

[tahonermann]

Removed the SG7 label per email discussion; SG7 related concerns will be discussed via P1953 (#690).

[tahonermann]

SG16 approved P1949R1 in Prague. Minutes are at http://wiki.edg.com/bin/view/Wg21prague/SG16P1949R1.

P1949R1: Implementations should implicitly normalize identifiers to NFC

SF	F	N	A	SA
1	2	2	3	0

Consensus? No

P1949R1: non-NFC normalized identifiers should be ill-formed.

SF	F	N	A	SA
4	4	0	0	0

Consensus? Yes

P1949R1: We agree with the stated UAX31 conformance requirements.

SF	F	N	A	SA
2	4	1	0	0

Consensus? Yes

P1949R1: Encourage exploring incorporation of UAX39; exclusion of confusables.

SF	F	N	A	SA
0	3	2	0	1

Consensus? Weak - authors prerogative

P1949R1: Forward to EWG

SF	F	N	A	SA
4	2	1	0	0

Adding the needs-revision tag to address SG16 guidance and to provide wording. SG16 guidance was to specify that non-NFC normalized identifiers are ill-formed.

[erichkeane]

EWGI in Prague

Given the time constraints of the committee, should we spend additional committee effort on
P1949?

SF	F	N	A	SA
12	3	1	0	0

Should implementers be allowed to extend the list of allowable characters as a conforming
extension?

SF	F	N	A	SA
1	1	7	4	0

We believe that P1949R1 has been sufficiently developed and (pending the feedback from the
room and SG16 are merged) this paper is ready for EWG.

SF	F	N	A	SA
8	6	1	0	0