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 #810 Date: Wed, 8 Jun 2022 11:52:45 +0000 (GMT) [thread overview] Message-ID: <20220608115245.BFE6339960D4@sourceware.org> (raw) https://gcc.gnu.org/g:0995184e26f81f8ba6872c3efb59f640a7fe7162 commit 0995184e26f81f8ba6872c3efb59f640a7fe7162 Merge: 63fc39600ce db832831ed1 Author: bors[bot] <26634292+bors[bot]@users.noreply.github.com> Date: Thu Nov 18 00:16:47 2021 +0000 Merge #810 810: Fix MethodCalls for covariant impl blocks r=philberty a=philberty I think we need to research more into how we probe for potential candidates for method calls. This fixes a few bugs going on in #808 one where the canonical path was empty and one where we fail to probe directly on the receiver of reference types to impl blocks but we must be able to also support that autoderef means that a receiver's root type might actually be the type we care about for example a reference to a generic type-parameter and we probe its bounds for candidates for example. Lets consult the rustc code and references on this. Fixes #808 Co-authored-by: Philip Herron <philip.herron@embecosm.com> Diff: gcc/rust/Make-lang.in | 1 + gcc/rust/resolve/rust-ast-resolve-type.h | 3 ++ gcc/rust/resolve/rust-ast-resolve.cc | 38 +++++++++++++++---- gcc/rust/typecheck/rust-hir-type-check-expr.h | 29 ++++++++++++--- gcc/rust/typecheck/rust-substitution-mapper.cc | 49 +++++++++++++++++++++++++ gcc/rust/typecheck/rust-substitution-mapper.h | 8 +--- gcc/rust/typecheck/rust-tyty-call.h | 9 +++-- gcc/rust/typecheck/rust-tyty.cc | 2 + gcc/testsuite/rust/compile/torture/issue-808.rs | 23 ++++++++++++ 9 files changed, 140 insertions(+), 22 deletions(-)
reply other threads:[~2022-06-08 11:52 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=20220608115245.BFE6339960D4@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).