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 #1316 Date: Tue, 21 Jun 2022 10:33:39 +0000 (GMT) [thread overview] Message-ID: <20220621103339.C09CE387086E@sourceware.org> (raw) https://gcc.gnu.org/g:76f7e45179de4e6e53caab104022cc0784ecd618 commit 76f7e45179de4e6e53caab104022cc0784ecd618 Merge: 848a1a28b91 594854ec08c Author: bors[bot] <26634292+bors[bot]@users.noreply.github.com> Date: Fri Jun 17 07:50:03 2022 +0000 Merge #1316 1316: Add const generic declaration to AST r=CohenArthur a=CohenArthur This uses a number of hacks and workarounds to avoid implementing the equivalent HIR node in the same PR. I'll raise issues for each of the `FIXME`s in the code. Needs one commit from #1315 to avoid unecessary conflicts. Co-authored-by: Arthur Cohen <arthur.cohen@embecosm.com> Diff: gcc/rust/ast/rust-ast-dump.cc | 4 ++ gcc/rust/ast/rust-ast-dump.h | 1 + gcc/rust/ast/rust-ast-full-decls.h | 1 + gcc/rust/ast/rust-ast-full-test.cc | 19 +++++++++ gcc/rust/ast/rust-ast-visitor.h | 1 + gcc/rust/ast/rust-ast.h | 66 +++++++++++++++++++++++++++++++ gcc/rust/expand/rust-attribute-visitor.cc | 5 +++ gcc/rust/expand/rust-attribute-visitor.h | 1 + gcc/rust/hir/rust-ast-lower-base.cc | 3 ++ gcc/rust/hir/rust-ast-lower-base.h | 1 + gcc/rust/hir/rust-ast-lower-type.h | 16 ++++++++ gcc/rust/parse/rust-parse-impl.h | 16 ++++---- gcc/rust/resolve/rust-ast-resolve-base.cc | 4 ++ gcc/rust/resolve/rust-ast-resolve-base.h | 1 + gcc/rust/resolve/rust-ast-resolve-type.h | 7 ++++ 15 files changed, 139 insertions(+), 7 deletions(-)
reply other threads:[~2022-06-21 10:33 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=20220621103339.C09CE387086E@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: linkBe 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).