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 #1632
Date: Mon,  5 Dec 2022 09:53:37 +0000 (GMT)	[thread overview]
Message-ID: <20221205095337.97E49389851A@sourceware.org> (raw)

https://gcc.gnu.org/g:9666f2b169b5192b5c827d605cc80e6987e1aac5

commit 9666f2b169b5192b5c827d605cc80e6987e1aac5
Merge: e39fadcd0aa 31dd14e197c
Author: bors[bot] <26634292+bors[bot]@users.noreply.github.com>
Date:   Mon Dec 5 01:22:10 2022 +0000

    Merge #1632
    
    1632: Fix mac-os regression in apply generic arguments to method calls r=philberty a=philberty
    
    When applying generic arguments to method calls such as:
    
    ```receiver.method_name<i32, bool>()```
    
    This ended up wrongly using the default constructor with an empty generic arguments which seems
    like a possible bug in the new version of clang. This explicitly sets up all relevant copy constructors
    for HIR::PathExprSegment and removes the defaults.
    
    Co-authored-by: Philip Herron <philip.herron@embecosm.com>

Diff:

 gcc/rust/hir/tree/rust-hir-expr.h              |  3 ++-
 gcc/rust/hir/tree/rust-hir-full-decls.h        |  2 +-
 gcc/rust/hir/tree/rust-hir-path.h              | 37 +++++++++++++++++++-------
 gcc/rust/typecheck/rust-hir-type-check-expr.cc |  5 ++--
 gcc/rust/typecheck/rust-tyty.h                 |  4 +++
 gcc/testsuite/rust/debug/chartype.rs           | 15 ++++++-----
 6 files changed, 46 insertions(+), 20 deletions(-)

                 reply	other threads:[~2022-12-05  9:53 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=20221205095337.97E49389851A@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).