Re: use «chevrons» to represent string literal

[Richard (Rikki) Andrew Cattermole]

On 17/01/2025 11:16 AM, barbosso wrote:
> On Thursday, 16 January 2025 at 22:03:25 UTC, barbosso wrote:
>> On Thursday, 16 January 2025 at 21:45:39 UTC, Richard (Rikki) Andrew 
>> Cattermole wrote:
>>> On 17/01/2025 10:43 AM, barbosso wrote:
>>>> On Thursday, 16 January 2025 at 21:38:50 UTC, Richard (Rikki) Andrew 
>>>> Cattermole wrote:
>>>>> [...]
>>>>
>>>> Do you understand what you wrote?
>>>
>>> Yes.
>>>
>>> Extended ASCII is both a character set and an encoding.
>>>
>>> The character set is supported as part of Unicode, the encoding is 
>>> not supported as we use UTF-8 which conflicts on the 8th bit for the 
>>> first byte in the code unit.
>>
>>
>> now I see.
>> UTF-8 use 1 byte to represent 128 characters ASCII
>> and 2 bytes for other characters (including «chevrons»).
>> So, what's the problem?
> 
> GCC and Clang can compile identifiers with Unicode symbols.

I know, I implemented D's UAX31 identifiers.

Better to have the right terminology for this.

However the current stance is that we have possibly too many string 
types. So far you have proposed new delimiters but not new behaviors 
(which would be required to add it).