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 #1771
Date: Mon, 30 Jan 2023 13:24:03 +0000 (GMT)	[thread overview]
Message-ID: <20230130132403.40CE13858C33@sourceware.org> (raw)

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

commit fe828b4f931ca216a4b74322a4fdb527faada53e
Merge: a91b12e2c4c 01a07f7d395
Author: bors[bot] <26634292+bors[bot]@users.noreply.github.com>
Date:   Thu Jan 26 15:28:46 2023 +0000

    Merge #1771
    
    1771: Add type resolution for grouped patterns r=philberty a=powerboat9
    
    Signed-off-by: Owen Avery <powerboat9.gamer@gmail.com>
    
    Adds type resolution for GroupedPattern.
    
    Co-authored-by: Owen Avery <powerboat9.gamer@gmail.com>

Diff:

 gcc/rust/hir/tree/rust-hir-pattern.h              | 6 ++++++
 gcc/rust/typecheck/rust-hir-type-check-pattern.cc | 8 +++++---
 2 files changed, 11 insertions(+), 3 deletions(-)

                 reply	other threads:[~2023-01-30 13: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=20230130132403.40CE13858C33@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).