Re: [GSoC] gccrs Unicode support

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

Re: [GSoC] gccrs Unicode support

On Sat, Mar 18, 2023 at 05:59:34PM +0900, Raiki Tamura wrote: > 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. > >> > >

Re: [GSoC] gccrs Unicode support

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 on XID_Start and XID_Continue? >

Re: [GSoC] gccrs Unicode support

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 on XID_Start and XID_Continue? That should already be supported.

Re: [GSoC] gccrs Unicode support

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 t

Re: [GSoC] gccrs Unicode support

On Thu, Mar 16, 2023 at 01:58:57PM +0100, Mark Wielaard wrote: > On Thu, 2023-03-16 at 10:28 +0100, Thomas Schwinge wrote: > > I'm now also putting Mark Wielaard in CC; he once also started discussing > > this topic, "thinking of importing a couple of gnulib modules to help > > with UTF-8 processin

Re: [GSoC] gccrs Unicode support

Hi, On Thu, 2023-03-16 at 10:28 +0100, Thomas Schwinge wrote: > I'm now also putting Mark Wielaard in CC; he once also started discussing > this topic, "thinking of importing a couple of gnulib modules to help > with UTF-8 processing [unless] other gcc frontends handle [these things] > already in

Re: [GSoC] gccrs Unicode support

Hi! (By the way, this GSoC project is being discussed in GCC/Rust Zulip: .) I'm now also putting Mark Wielaard in CC; he once also started discussing this topic, "thinking of importing a couple of gnulib modules to

Re: [GSoC] gccrs Unicode support

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 t

Re: [GSoC] gccrs Unicode support

On Wed, Mar 15, 2023 at 11:00:19AM +, Philip Herron via Gcc wrote: > Excellent work on getting up to speed on the rust front-end. From my > perspective I am interested to see what the wider GCC community thinks > about using https://www.gnu.org/software/libunistring/ library within GCC > instea

Re: [GSoC] gccrs Unicode support

Philip Herron via Gcc writes: > Hi Raiki Welcome, Raiki! > Excellent work on getting up to speed on the rust front-end. From my > perspective I am interested to see what the wider GCC community thinks > about using https://www.gnu.org/software/libunistring/ library within GCC > instead of roll

Re: [GSoC] gccrs Unicode support

Hi Raiki Excellent work on getting up to speed on the rust front-end. From my perspective I am interested to see what the wider GCC community thinks about using https://www.gnu.org/software/libunistring/ library within GCC instead of rolling our own, this means it will be another dependency on GCC