Subject: Re: Concatenating unicode string literals
From: Alisdair Meredith (alisdairm_at_[hidden])
Date: 2020-07-08 12:39:55
Yup - this is why I dropped Core from the CC list and sent it to just SG16 :)
I would like to hear whether SG16 thought the problem worth solving
before investing any time in it though - otherwise there is no end to the
list of things we can polish in C++ with unlimited resources!
> On Jul 8, 2020, at 17:40, Jens Maurer via SG16 <sg16_at_[hidden]> wrote:
> On 08/07/2020 18.37, Jens Maurer via SG16 wrote:
>> On 08/07/2020 13.09, Alisdair Meredith via SG16 wrote:
>>> After taking another look over P2029 resolving a few core issues,
>>> I am further concerned by [lex.string]p11, which states (among
>>> other things) that concatenation of unicode string literals with
>>> different encoding-prefixes is conditionally supported with
>>> implementation-defined behavior. That seems a little to free for
>>> my tastes.
>> This is pre-existing and unchanged from the status quo.
>> [lex.string] p11
>> "Any other concatenations are conditionally-supported with implementation-defined behavior."
>> If you want a change here, it should be a separate paper.
> I just realized you're not asking this be addressed in P2029.
> Please excuse my confusion.
> SG16 mailing list
SG16 list run by firstname.lastname@example.org