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 #1735
Date: Mon, 30 Jan 2023 17:24:59 +0000 (GMT)	[thread overview]
Message-ID: <20230130172459.8D8893858C1F@sourceware.org> (raw)

https://gcc.gnu.org/g:d7c321da9f8fdee4527285c782db57c7c4d520e4

commit d7c321da9f8fdee4527285c782db57c7c4d520e4
Merge: 0ae13efb5a6 3630e0e2bf0
Author: bors[bot] <26634292+bors[bot]@users.noreply.github.com>
Date:   Mon Jan 30 12:44:25 2023 +0000

    Merge #1735
    
    1735: macro: Allow builtin `MacroInvocation`s within the AST r=CohenArthur a=CohenArthur
    
    gcc/rust/ChangeLog:
    
            * ast/rust-macro.h (enum class): Add `BuiltinMacro` enum class
            * expand/rust-attribute-visitor.cc (AttrVisitor::visit): Mention switching on `macro.kind` once builtin macro invocations are properly handled
            * parse/rust-parse-impl.h (Parser::parse_macro_invocation): Switch to new MacroInvocation API
            (Parser::parse_type): Switch to new MacroInvocation API
            (Parser::parse_type_no_bounds): Switch to new MacroInvocation API
    
    This will be necessary for proper handling of builtin macros with the new `EarlyNameResolver` class and associated fixed-point algorithm
    
    Co-authored-by: Arthur Cohen <arthur.cohen@embecosm.com>

Diff:

 gcc/rust/ast/rust-macro.h                 | 110 +++++++++++++++++++++++++-----
 gcc/rust/expand/rust-attribute-visitor.cc |   2 +
 gcc/rust/parse/rust-parse-impl.h          |  70 +++++++++----------
 3 files changed, 126 insertions(+), 56 deletions(-)

                 reply	other threads:[~2023-01-30 17:24 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=20230130172459.8D8893858C1F@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).