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 #940 Date: Wed, 8 Jun 2022 12:08:55 +0000 (GMT) [thread overview] Message-ID: <20220608120855.F0E633817D11@sourceware.org> (raw) https://gcc.gnu.org/g:fbe22e87687c68357430e60361a8a124c81148cc commit fbe22e87687c68357430e60361a8a124c81148cc Merge: 9fb06d66cef 0e15b898391 Author: bors[bot] <26634292+bors[bot]@users.noreply.github.com> Date: Fri Feb 18 08:14:30 2022 +0000 Merge #940 940: Add more location info to AST structures r=CohenArthur a=CohenArthur Two classes still remain locus-less: `TupleStructItems` and `TuplePatternItems` as I do not believe they are constructed at the moment. Co-authored-by: Arthur Cohen <arthur.cohen@embecosm.com> Diff: gcc/rust/ast/rust-expr.h | 35 +++++++++++++------------ gcc/rust/ast/rust-item.h | 9 +++---- gcc/rust/ast/rust-path.h | 35 +++++++++++++++---------- gcc/rust/ast/rust-pattern.h | 6 ++--- gcc/rust/parse/rust-parse-impl.h | 51 +++++++++++++++++++++--------------- gcc/rust/parse/rust-parse.h | 2 +- gcc/rust/resolve/rust-ast-resolve.cc | 2 +- 7 files changed, 78 insertions(+), 62 deletions(-)
reply other threads:[~2022-06-08 12:08 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=20220608120855.F0E633817D11@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).