From: Raiki Tamura <tamaron1203@gmail.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Arthur Cohen <arthur.cohen@embecosm.com>,
David Edelsohn <dje.gcc@gmail.com>,
Philip Herron <herron.philip@googlemail.com>,
gcc@gcc.gnu.org, gcc-rust@gcc.gnu.org
Subject: Re: [GSoC] gccrs Unicode support
Date: Thu, 16 Mar 2023 17:57:04 +0900 [thread overview]
Message-ID: <CAOWUKr20VOOuQpV-OK2a4XG7rFyZRzXguWbsQDH099dsQV5m2Q@mail.gmail.com> (raw)
In-Reply-To: <ZBHhutUTOl26A13z@tucnak>
[-- Attachment #1: Type: text/plain, Size: 1669 bytes --]
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 the hope that it can also
be used in the Rust frontend.
Raiki Tamura
On Thu, Mar 16, 2023 at 0:18 Jakub Jelinek <jakub@redhat.com> wrote:
> On Wed, Mar 15, 2023 at 11:00:19AM +0000, 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
> > instead of rolling our own, this means it will be another dependency on
> GCC.
> >
> > The other option is there is already code in the other front-ends to do
> > this so in the worst case it should be possible to extract something out
> of
> > them and possibly make this a shared piece of functionality which we can
> > mentor you through.
>
> I don't know what exactly Rust FE needs in this area, but e.g. libcpp
> already handles whatever C/C++ need from Unicode support POV and can handle
> it without any extra libraries.
> So, if we could avoid the extra dependency, it would be certainly better,
> unless you really need massive amounts of code from those libraries.
> libcpp already e.g. provides mapping of unicode character names to code
> points, determining which unicode characters can appear at the start or
> in the middle of identifiers, etc.
>
> Jakub
>
>
next prev parent reply other threads:[~2023-03-16 8:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-18 13:22 rust frontend and UTF-8/unicode processing/properties Mark Wielaard
2021-07-18 20:12 ` Ian Lance Taylor
2021-07-18 22:23 ` Jason Merrill
2021-07-23 11:29 ` Philip Herron
2021-07-29 19:46 ` Manuel López-Ibáñez
2023-03-13 16:18 ` [GSoC] gccrs Unicode support Raiki Tamura
2023-03-15 11:00 ` Philip Herron
2023-03-15 14:53 ` Arsen Arsenović
2023-03-15 15:18 ` Jakub Jelinek
2023-03-16 8:57 ` Raiki Tamura [this message]
2023-03-16 9:28 ` Thomas Schwinge
2023-03-16 12:58 ` Mark Wielaard
2023-03-16 13:07 ` Jakub Jelinek
2023-03-18 8:31 ` Raiki Tamura
2023-03-18 8:47 ` Jonathan Wakely
2023-03-18 8:59 ` Raiki Tamura
2023-03-18 9:28 ` Jakub Jelinek
2023-03-20 10:19 ` Raiki Tamura
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=CAOWUKr20VOOuQpV-OK2a4XG7rFyZRzXguWbsQDH099dsQV5m2Q@mail.gmail.com \
--to=tamaron1203@gmail.com \
--cc=arthur.cohen@embecosm.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-rust@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=herron.philip@googlemail.com \
--cc=jakub@redhat.com \
/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).