Title
UTF-16 in char16_t string literals
Status
cd5
Section
5.13.5 [lex.string]
Submitter
Richard Smith

Created on 2014-02-12.00:00:00 last changed 5 months ago

Messages

Date: 2019-02-15.00:00:00

Rationale (February, 2019)

The Standard is now clear on this point.

Date: 2019-02-15.00:00:00

[Adopted at the February, 2019 meeting as part of paper P1041R4.]

The resolution of issue 1802 clarified that char16_t string literals can contain surrogate pairs, in contrast to char16_t character literals. However, there is no explicit requirement that char16_t literals be encoded as UTF-16, although that is explicitly stated for char16_t character literals, so it's not clear what the value is required to be in the surrogate-pair case.

History
Date User Action Args
2021-02-17 00:00:00adminsetstatus: nad -> cd5
2020-12-15 00:00:00adminsetmessages: + msg6290
2020-12-15 00:00:00adminsetstatus: drafting -> nad
2014-07-07 00:00:00adminsetstatus: open -> drafting
2014-02-12 00:00:00admincreate