public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rust/108111] Rust meets clang Date: Tue, 16 Jan 2024 17:24:20 +0000 [thread overview] Message-ID: <bug-108111-4-da3ogoTzst@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108111-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108111 --- Comment #4 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The trunk branch has been updated by Arthur Cohen <cohenarthur@gcc.gnu.org>: https://gcc.gnu.org/g:2046aec032f743023a5e353735255d951e2e54d6 commit r14-7347-g2046aec032f743023a5e353735255d951e2e54d6 Author: Marc Poulhiès <dkm@kataplop.net> Date: Sat Dec 17 16:23:05 2022 +0100 gccrs: fix some clang warnings This fixes some extra warnings reported by clang. gcc/rust/ChangeLog: PR rust/108111 * ast/rust-ast-full-decls.h (StructPatternElements): Declare as a class. * ast/rust-item.h (EnumItem): Mark several method as being overrides. * ast/rust-pattern.h (StructPattern::get_locus): Add override. * lex/rust-lex.h (BufferInputSource): Use reference_wrapper instead of bare reference. (TokenSource::get): Add method to implement the reference_wrapper interface. * typecheck/rust-tyty.h (TypeBoundPredicate): Add empty dtor. * util/rust-buffered-queue.h (peek): Source token stream is now using a reference_wrapper, use .get() Signed-off-by: Marc Poulhiès <dkm@kataplop.net>
prev parent reply other threads:[~2024-01-16 17:24 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-14 19:17 [Bug rust/108111] New: " dcb314 at hotmail dot com 2022-12-14 21:46 ` [Bug rust/108111] " dkm at gcc dot gnu.org 2022-12-14 22:22 ` redi at gcc dot gnu.org 2022-12-15 10:44 ` marxin at gcc dot gnu.org 2022-12-15 20:22 ` dkm at gcc dot gnu.org 2024-01-16 17:24 ` cvs-commit at gcc dot gnu.org [this message]
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=bug-108111-4-da3ogoTzst@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).