Re: C11: should we use char32_t for unicode code points? - Mailing list pgsql-hackers

From Jeff Davis
Subject Re: C11: should we use char32_t for unicode code points?
Date
Msg-id 435cf6bcf14bb91235da065c70d782863ca9b80e.camel@j-davis.com
Whole thread Raw
In response to Re: C11: should we use char32_t for unicode code points?  (Tatsuo Ishii <ishii@postgresql.org>)
Responses Re: C11: should we use char32_t for unicode code points?
List pgsql-hackers
On Fri, 2025-10-24 at 18:43 +0900, Tatsuo Ishii wrote:
>
> Unless char32_t is solely used for the Unicode code point data, I
> think it would be better to define something like "pg_unicode" and
> use
> it instead of directly using char32_t because it would be cleaner for
> code readers.

That was my original idea, but then I saw that apparently char32_t is
intended for Unicode code points:

https://www.gnu.org/software/gnulib/manual/html_node/The-char32_005ft-type.html

But I am also OK with a new type if others find it more readable.

Regards,
    Jeff Davis




pgsql-hackers by date:

Previous
From: vignesh C
Date:
Subject: Re: Logical Replication of sequences
Next
From: Nathan Bossart
Date:
Subject: Re: Remove Item type