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 #1336
Date: Thu, 30 Jun 2022 18:51:13 +0000 (GMT)	[thread overview]
Message-ID: <20220630185113.5E497383EC61@sourceware.org> (raw)

https://gcc.gnu.org/g:33912c1a08d3892d3c72506aed38771754b9cf54

commit 33912c1a08d3892d3c72506aed38771754b9cf54
Merge: 81abc8623cb 93f63a94d43
Author: bors[bot] <26634292+bors[bot]@users.noreply.github.com>
Date:   Thu Jun 30 15:52:01 2022 +0000

    Merge #1336
    
    1336: Resolve const generic parameters r=CohenArthur a=CohenArthur
    
    Fixes #1319.
    
    This can only resolve the simpler test cases: Anything that is ambiguous is ignored and does not get resolved. This will be fixed very soon :)
    
    Co-authored-by: Arthur Cohen <arthur.cohen@embecosm.com>

Diff:

 gcc/rust/ast/rust-ast-full-test.cc             |  4 +-
 gcc/rust/ast/rust-ast.h                        | 69 -------------------
 gcc/rust/ast/rust-path.h                       | 77 ++++++++++++++++++++-
 gcc/rust/hir/rust-ast-lower-type.h             | 12 ++--
 gcc/rust/parse/rust-parse-impl.h               |  2 +-
 gcc/rust/resolve/rust-ast-resolve-item.cc      | 95 ++++++++------------------
 gcc/rust/resolve/rust-ast-resolve-item.h       | 11 ++-
 gcc/rust/resolve/rust-ast-resolve-stmt.cc      |  2 +-
 gcc/rust/resolve/rust-ast-resolve-stmt.h       | 26 ++-----
 gcc/rust/resolve/rust-ast-resolve-type.h       | 27 ++++++--
 gcc/testsuite/rust/compile/const_generics_4.rs |  7 ++
 11 files changed, 161 insertions(+), 171 deletions(-)


                 reply	other threads:[~2022-06-30 18:51 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=20220630185113.5E497383EC61@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).