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 #1724 Date: Thu, 12 Jan 2023 07:44:59 +0000 (GMT) [thread overview] Message-ID: <20230112074459.F41F13854388@sourceware.org> (raw) https://gcc.gnu.org/g:b6fcee808fd654d2d5c13b87565f1e59cc61a138 commit b6fcee808fd654d2d5c13b87565f1e59cc61a138 Merge: 3290293e16f ed6718d979e Author: bors[bot] <26634292+bors[bot]@users.noreply.github.com> Date: Tue Jan 10 22:39:41 2023 +0000 Merge #1724 1724: Add support for generics associated type binding r=philberty a=philberty This patch set adds support to specify the associated type via the argument binding syntax. We are still missing general bounds checking so in order to properly add more test cases for bad types we need to implement that first. I have also changed a test case to -fsyntax-only as at the time I always get confused between Generic arguments of foo=i32 and bar: baz only specifies the associated type and the latter adds a bound. Currently we are lacking a way to represent adding a bound in the AST and HIR within generic arguments so I have raised: #1725 and #1726 Fixes #1720 Co-authored-by: Philip Herron <herron.philip@googlemail.com> Diff: gcc/rust/hir/tree/rust-hir-path.h | 4 +- gcc/rust/resolve/rust-ast-resolve-type.cc | 5 ++ gcc/rust/typecheck/rust-hir-path-probe.h | 3 +- gcc/rust/typecheck/rust-hir-trait-resolve.cc | 11 +-- gcc/rust/typecheck/rust-hir-type-check-expr.cc | 12 ++-- gcc/rust/typecheck/rust-tyty-bounds.cc | 89 +++++++++++++++++++++--- gcc/rust/typecheck/rust-tyty.cc | 73 ++++++++++++++++--- gcc/rust/typecheck/rust-tyty.h | 48 +++++++++++-- gcc/testsuite/rust/compile/bounds.rs | 8 ++- gcc/testsuite/rust/execute/torture/issue-1720.rs | 26 +++++++ 10 files changed, 241 insertions(+), 38 deletions(-)
reply other threads:[~2023-01-12 7:44 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=20230112074459.F41F13854388@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).