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 #1008 #1009 Date: Wed, 8 Jun 2022 12:18:09 +0000 (GMT) [thread overview] Message-ID: <20220608121809.7DB0B3852742@sourceware.org> (raw) https://gcc.gnu.org/g:6e64e6636ef823ac97ad889b71bb792fbe510580 commit 6e64e6636ef823ac97ad889b71bb792fbe510580 Merge: dbe59a31984 a1b065050ba 894e9d29ada Author: bors[bot] <26634292+bors[bot]@users.noreply.github.com> Date: Fri Mar 11 10:39:24 2022 +0000 Merge #1008 #1009 1008: Add const_ptr lang item mappings r=philberty a=philberty In order to support slices, we need to be able to parse and contain mappings for the const_ptr lang item. We do not need to do any special handling of this lang item yet but this adds the mappings so when we hit it we do not output an unknown lang item error. Addresses #849 1009: Add missing type resolution to slices and arrays r=philberty a=philberty This adds in the missing type resolution for slices and generic slices and arrays. Since Arrays and Slices are both covariant types just like references and pointers for example they need to handle recursive substitutions where their element type might be a generic type that can bind substitution parameters such as functions and ADT's. Addresses #849 Co-authored-by: Philip Herron <philip.herron@embecosm.com> Diff: gcc/rust/hir/tree/rust-hir-type.h | 2 ++ gcc/rust/typecheck/rust-hir-type-check-type.cc | 10 ++++++++ gcc/rust/typecheck/rust-hir-type-check-type.h | 6 +++-- gcc/rust/typecheck/rust-substitution-mapper.h | 12 ++++++++-- gcc/rust/typecheck/rust-tyty.cc | 32 ++++++++++++++++++++++++++ gcc/rust/typecheck/rust-tyty.h | 4 ++++ gcc/rust/util/rust-lang-item.h | 9 ++++++++ 7 files changed, 71 insertions(+), 4 deletions(-)
reply other threads:[~2022-06-08 12:18 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=20220608121809.7DB0B3852742@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).