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 #1215 Date: Wed, 8 Jun 2022 12:44:29 +0000 (GMT) [thread overview] Message-ID: <20220608124429.1EF8D38936EC@sourceware.org> (raw) https://gcc.gnu.org/g:74e836599ce80a11b1fe28065ed7aae6ffa3b7e2 commit 74e836599ce80a11b1fe28065ed7aae6ffa3b7e2 Merge: 9ea940e4dca 2df8cf57e62 Author: bors[bot] <26634292+bors[bot]@users.noreply.github.com> Date: Fri May 6 12:56:12 2022 +0000 Merge #1215 1215: Report `pub restricted` violations r=CohenArthur a=CohenArthur Needs #1202. The only commit worth reviewing in the meantime is [c229c7f](https://github.com/Rust-GCC/gccrs/pull/1215/commits/c229c7f891f02c3ecd1c7b743b35edb3fc2c5539) This visitor allows us to report invalid restrictions in `pub(restricted)` visibilities. I've added documentation and an example to the visitor to explain the expected behavior. Co-authored-by: Arthur Cohen <arthur.cohen@embecosm.com> Diff: gcc/rust/Make-lang.in | 1 + gcc/rust/hir/tree/rust-hir-full-test.cc | 2 + gcc/rust/privacy/rust-privacy-check.cc | 8 +- gcc/rust/privacy/rust-pub-restricted-visitor.cc | 178 ++++++++++++++++++++++++ gcc/rust/privacy/rust-pub-restricted-visitor.h | 120 ++++++++++++++++ gcc/rust/privacy/rust-visibility-resolver.cc | 17 +-- gcc/rust/privacy/rust-visibility-resolver.h | 3 - gcc/testsuite/rust/compile/pub_restricted_2.rs | 18 +++ 8 files changed, 325 insertions(+), 22 deletions(-)
reply other threads:[~2022-06-08 12: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=20220608124429.1EF8D38936EC@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).