C++ Logo

sg16

Advanced search

Re: Feedback on D2513R1: char8_t Compatibility and Portability Fix

From: Hubert Tong <hubert.reinterpretcast_at_[hidden]>
Date: Thu, 10 Feb 2022 19:35:26 -0500
On Thu, Feb 10, 2022 at 7:28 PM Jens Maurer <Jens.Maurer_at_[hidden]> wrote:

> On 11/02/2022 01.13, Hubert Tong via SG16 wrote:
> > Link to paper: https://thephd.dev/_vendor/future_cxx/papers/d1967.html <
> https://thephd.dev/_vendor/future_cxx/papers/d1967.html>
> >
> > Quote from proposed wording:
> >
> > Additionally, an array of ordinary character type may be initialized
> by a UTF-8 string literal, or by such a string literal enclosed in braces.
> Successive characters of the value of the string-literal initialize the
> elements of the array.
> >
> >
> > The wording does not address the case of UTF-8 code units in the value
> of the u8 string literal with numerical values that exceed the range of
> values representable by signed char.
>
> This might be a pre-existing defect, but we don't address that case for a
> regular
> string literal (on a platform where char happens to be unsigned), either.
>

I think the time-honoured tradition of having people address at least some
defects while "in the area" is reasonable to apply here.


>
> Jens
>

Received on 2022-02-11 00:35:54