public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Thomas Schwinge <tschwinge@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc/devel/rust/master] Merge #1042
Date: Wed,  8 Jun 2022 12:21:37 +0000 (GMT)	[thread overview]
Message-ID: <20220608122137.C7EB8382B24C@sourceware.org> (raw)

https://gcc.gnu.org/g:32894e6986523cb6b0d4225f820d80a725546c3a

commit 32894e6986523cb6b0d4225f820d80a725546c3a
Merge: 1bb9a29688a 80d96902421
Author: bors[bot] <26634292+bors[bot]@users.noreply.github.com>
Date:   Mon Mar 21 12:41:52 2022 +0000

    Merge #1042
    
    1042: Parse reserved keywords as valid fragments identifiers r=CohenArthur a=CohenArthur
    
    Per the reference, macro fragments actually accept all identifiers, not
    NON_KEYWORD_IDENTIFIERS
    
    Fixes #1013
    
    Co-authored-by: Arthur Cohen <arthur.cohen@embecosm.com>

Diff:

 gcc/rust/parse/rust-parse-impl.h | 62 ++++++++++++++++++++++++++++++++++++++--
 1 file changed, 59 insertions(+), 3 deletions(-)


                 reply	other threads:[~2022-06-08 12:21 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20220608122137.C7EB8382B24C@sourceware.org \
    --to=tschwinge@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.org \
    /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).