Created on 2014-02-12.00:00:00 last changed 45 months ago
Rationale (February, 2019)
The Standard is now clear on this point.
[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:00 | admin | set | status: nad -> cd5 |
| 2020-12-15 00:00:00 | admin | set | messages: + msg6290 |
| 2020-12-15 00:00:00 | admin | set | status: drafting -> nad |
| 2014-07-07 00:00:00 | admin | set | status: open -> drafting |
| 2014-02-12 00:00:00 | admin | create | |