From: Raiki Tamura <tamaron1203@gmail.com>
To: Mark Wielaard <mark@klomp.org>
Cc: "Thomas Schwinge" <thomas@codesourcery.com>,
"Jakub Jelinek" <jakub@redhat.com>,
"Philip Herron" <herron.philip@googlemail.com>,
gcc@gcc.gnu.org, gcc-rust@gcc.gnu.org,
"David Edelsohn" <dje.gcc@gmail.com>,
"Arthur Cohen" <arthur.cohen@embecosm.com>,
"Arsen Arsenović" <arsen@aarsen.me>
Subject: Re: [GSoC] gccrs Unicode support
Date: Sat, 18 Mar 2023 17:31:44 +0900 [thread overview]
Message-ID: <CAOWUKr2Yj6yyzU3e5z=oEnhS9C8f+Me+taUzUhNvhzqHmLvdVA@mail.gmail.com> (raw)
In-Reply-To: <a476e56f825e8570a3f885491f871469879305c6.camel@klomp.org>
[-- Attachment #1: Type: text/plain, Size: 841 bytes --]
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 to add missing rows to
the table and use it in the Rust frontend.
2023年3月16日(木) 21:59 Mark Wielaard <mark@klomp.org>:
> You might want to research whether NFC normalization of identifiers is
> required to be done by the lexer or parser in Rust and how it interacts
> with proc macros.
Yes, NFC normalization must be done by the lexer, which may be complex and
hard to implement.
libunistring can also be used for normalization, so is it good to use
libunistring only in the normalization process?
Raiki Tamura
next prev parent reply other threads:[~2023-03-18 8:31 UTC|newest]
Thread overview: 17+ 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
[not found] ` <d5e7434b-80e8-2817-ed87-a23ef2ac0cbb@uma.es>
[not found] ` <CAOWUKr0Sd3RRSy2cuqMLj--KTWqOz=nQMxmx7ahM8YunrFzEig@mail.gmail.com>
2023-03-15 11:00 ` [GSoC] gccrs Unicode support Philip Herron
2023-03-15 14:53 ` Arsen Arsenović
2023-03-15 15:18 ` Jakub Jelinek
2023-03-16 8:57 ` Raiki Tamura
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 [this message]
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
2023-03-31 10:27 [GSoC] gccrs Unicode Support E M
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='CAOWUKr2Yj6yyzU3e5z=oEnhS9C8f+Me+taUzUhNvhzqHmLvdVA@mail.gmail.com' \
--to=tamaron1203@gmail.com \
--cc=arsen@aarsen.me \
--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 \
--cc=mark@klomp.org \
--cc=thomas@codesourcery.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).