2023年3月18日(土) 18:28 Jakub Jelinek :
> That is a pretty simple thing, so no need to use an extra library for that.
> As is documented in contrib/unicode/README, the Unicode *.txt files are
> already checked in and there are several generators of tables.
> libcpp/makeucnid.cc already creates tables
Sorry for resending this email. I forgot using “Reply All”.
Thank you for your response, Arsen and Jakub.
I did not know C++ also supports Unicode identifiers.
I looked a little into C++ and found C++ accepts the same form of
identifiers as Rust.
So I will do further investigation of libcpp with
Thank you everyone for your advice.
Some kinds of names are restricted to unicode alphabetic/numeric in Rust.
And the current definition of the table defined in libcpp/ucind.h lacks
some rows representing which characters are alphabetic/numeric.
But it is not a problem because it seems to be easy
2023年3月18日(土) 17:47 Jonathan Wakely :
> On Sat, 18 Mar 2023, 08:32 Raiki Tamura via Gcc, wrote:
>
>> Thank you everyone for your advice.
>> Some kinds of names are restricted to unicode alphabetic/numeric in Rust.
>>
>
> Doesn't it use the same rules as C++, based
Hello,
My name is Raiki Tamura, an undergraduate student at Kyoto University in
Japan and I want to work on Unicode support in gccrs this year.
I have already written my proposal (linked below) and shared it with the
gccrs team in Zulip.
In the project, I am planning to use the GNU unistring
Sorry for resending this email. I forgot using “Reply All”.
Thank you for your response, Arsen and Jakub.
I did not know C++ also supports Unicode identifiers.
I looked a little into C++ and found C++ accepts the same form of
identifiers as Rust.
So I will do further investigation of libcpp with
Thank you everyone for your advice.
Some kinds of names are restricted to unicode alphabetic/numeric in Rust.
And the current definition of the table defined in libcpp/ucind.h lacks
some rows representing which characters are alphabetic/numeric.
But it is not a problem because it seems to be easy
