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 #1517
Date: Wed, 31 Aug 2022 13:57:57 +0000 (GMT) [thread overview]
Message-ID: <20220831135757.5B63F385C33A@sourceware.org> (raw)
https://gcc.gnu.org/g:9b210f1c544ce4b0a4ff330c1e93d3ee83785484
commit 9b210f1c544ce4b0a4ff330c1e93d3ee83785484
Merge: ebb127f2aed 5a0c27cb799
Author: bors[bot] <26634292+bors[bot]@users.noreply.github.com>
Date: Wed Aug 31 12:50:21 2022 +0000
Merge #1517
1517: Refactor error handling on unify r=philberty a=philberty
This is the first pass on a refactor for error handling on unify sites. Eventually we
will be able to get rid of our can_eq interface but this is the first pass to abstract
unify's to use this interface.
Eventually, we will have unify and unify_and_commit. Unify will become our can_eq
interface but will require more helpers around inference variables.
Co-authored-by: Philip Herron <philip.herron@embecosm.com>
Diff:
gcc/rust/typecheck/rust-autoderef.cc | 15 +-
gcc/rust/typecheck/rust-coercion.cc | 62 ++++-
gcc/rust/typecheck/rust-hir-dot-operator.cc | 15 ++
gcc/rust/typecheck/rust-hir-trait-resolve.cc | 24 +-
gcc/rust/typecheck/rust-hir-type-check-base.cc | 54 ++++-
gcc/rust/typecheck/rust-hir-type-check-base.h | 14 +-
gcc/rust/typecheck/rust-hir-type-check-enumitem.cc | 12 +-
gcc/rust/typecheck/rust-hir-type-check-expr.cc | 174 ++++++++++----
gcc/rust/typecheck/rust-hir-type-check-expr.h | 2 +-
gcc/rust/typecheck/rust-hir-type-check-implitem.cc | 17 +-
gcc/rust/typecheck/rust-hir-type-check-item.cc | 11 +-
gcc/rust/typecheck/rust-hir-type-check-path.cc | 5 +-
gcc/rust/typecheck/rust-hir-type-check-pattern.cc | 4 +-
gcc/rust/typecheck/rust-hir-type-check-stmt.cc | 39 ++-
gcc/rust/typecheck/rust-hir-type-check-struct.cc | 41 +++-
gcc/rust/typecheck/rust-hir-type-check-toplevel.cc | 24 +-
gcc/rust/typecheck/rust-hir-type-check-type.cc | 8 +-
gcc/rust/typecheck/rust-hir-type-check.cc | 12 +-
gcc/rust/typecheck/rust-tyctx.cc | 3 +
gcc/rust/typecheck/rust-tyty-call.cc | 46 +++-
gcc/rust/typecheck/rust-tyty-cmp.h | 4 +-
gcc/rust/typecheck/rust-tyty-rules.h | 264 ++-------------------
gcc/rust/typecheck/rust-tyty.cc | 66 +++++-
gcc/rust/typecheck/rust-tyty.h | 47 +---
gcc/testsuite/rust/compile/issue-1152.rs | 2 -
gcc/testsuite/rust/compile/tuple1.rs | 2 +-
gcc/testsuite/rust/compile/type-alias1.rs | 2 +-
.../rust/execute/torture/operator_overload_9.rs | 2 +-
gcc/testsuite/rust/execute/torture/slice1.rs | 7 +-
29 files changed, 571 insertions(+), 407 deletions(-)
reply other threads:[~2022-08-31 13:57 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=20220831135757.5B63F385C33A@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).