public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Tom Honermann <tom@honermann.net>
To: libc-alpha <libc-alpha@sourceware.org>
Subject: Re: [PATCH 0/3]: C++20 P0482R6 and C2X N2653: support for char8_t, mbrtoc8(), and c8rtomb().
Date: Wed, 23 Mar 2022 11:32:28 -0400	[thread overview]
Message-ID: <6dd08707-44b9-7c71-29c0-1a072d1e39a3@honermann.net> (raw)
In-Reply-To: <d6ac90a2-7bb3-3f21-abd7-8695a1cec835@honermann.net>

Is there anything I can do to help land this patch series? I believe all 
review comments have been addressed.

Tom.

On 2/27/22 11:53 AM, Tom Honermann via Libc-alpha wrote:
> This series of patches provides the following:
> - A fix for bug 25744 [1].
> - Implementations of the mbrtoc8 and c8rtomb functions adopted for
>   C++20 via WG21 P0482R6 [2] and for C2X via WG14 N2653 [3].
> - A char8_t typedef as adopted for C2X via WG14 N2653 [3].
>
> These patches addresses feedback provided in response to a previous 
> submission [4].
>
> Patch 1: A fix and test for bug 25744 [1].
> Patch 2: Definitions of the mbrtoc8 and c8rtomb functions and the
>          char8_t typedef.
> Patch 3: Tests for the mbrtoc8 and c8rtomb functions and the char8_t
>          typedef.
>
> The fix for bug 25744 [1] is included in this patch series because the 
> tests for mbrtoc8 and c8rtomb depend on it for exercising the special 
> case where a pair of Unicode code points is converted to/from a single 
> double byte sequence. Such conversion cases exist for Big5-HKSCS.
>
> N2653 was adopted by WG14 for C2X during their recent meeting. This 
> patch series enables the new declarations in C2X mode and when 
> _GNU_SOURCE is defined.
>
> Thank you to Joseph Myers and Carlos O'Donell for their prior reviews 
> of this patch series.
>
> Tom.
>
> [1]: Bug 25744
>      "mbrtowc with Big5-HKSCS returns 2 instead of 1 when consuming the
>      second byte of certain double byte characters"
>      https://sourceware.org/bugzilla/show_bug.cgi?id=25744
>
> [2]: WG21 P0482R6
>      "char8_t: A type for UTF-8 characters and strings (Revision 6)"
>      https://wg21.link/p0482r6
>
> [3]: WG14 N2653
>      "char8_t: A type for UTF-8 characters and strings (Revision 1)"
>      http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2653.htm
>
> [4]: "[PATCH 2/3]: C++20 P0482R6 and C2X N2653: Implement mbrtoc8,
>      c8rtomb, char8_t"
> https://sourceware.org/pipermail/libc-alpha/2022-February/136558.html

  reply	other threads:[~2022-03-23 15:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-27 16:53 Tom Honermann
2022-03-23 15:32 ` Tom Honermann [this message]
2022-05-16 16:04   ` Tom Honermann
  -- strict thread matches above, loose matches on Subject: below --
2022-01-08  0:39 Tom Honermann
2021-06-07  2:07 Tom Honermann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6dd08707-44b9-7c71-29c0-1a072d1e39a3@honermann.net \
    --to=tom@honermann.net \
    --cc=libc-alpha@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).