From: Raiki Tamura <tamaron1203@gmail.com>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: "Mark Wielaard" <mark@klomp.org>,
"Thomas Schwinge" <thomas@codesourcery.com>,
"Jakub Jelinek" <jakub@redhat.com>,
"Philip Herron" <herron.philip@googlemail.com>,
"gcc@gcc.gnu.org" <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:59:34 +0900 [thread overview]
Message-ID: <CAOWUKr3YZsXJkjEHHx42BB=R0JQO5NorRDRD5-AcT-NXYUC3uw@mail.gmail.com> (raw)
In-Reply-To: <CAH6eHdTGG2xGrHdqFyA6izfByxr5GtZ01ufRx-a+ufDq-OToGA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 752 bytes --]
2023年3月18日(土) 17:47 Jonathan Wakely <jwakely.gcc@gmail.com>:
> On Sat, 18 Mar 2023, 08:32 Raiki Tamura via Gcc, <gcc@gcc.gnu.org> 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.
>
Yes, C++ and Rust use the same rules for identifiers (described in UAX#31)
and we can reuse it in the lexer of gccrs.
I was talking about values of Rust's crate_name attributes, which only
allow Unicode alphabetic/numeric characters.
(Ref:
https://doc.rust-lang.org/reference/crates-and-source-files.html#the-crate_name-attribute
)
Raiki Tamura
next prev parent reply other threads:[~2023-03-18 8:59 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
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 [this message]
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='CAOWUKr3YZsXJkjEHHx42BB=R0JQO5NorRDRD5-AcT-NXYUC3uw@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=jwakely.gcc@gmail.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).