public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Iain Buclaw <ibuclaw@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r12-8970] d: Remove "final" and "override" from visitor method. Date: Sun, 11 Dec 2022 18:14:17 +0000 (GMT) [thread overview] Message-ID: <20221211181417.1D6F43832E57@sourceware.org> (raw) https://gcc.gnu.org/g:db8e3439ae4089ac27e542ff8f9e64a7aa093d67 commit r12-8970-gdb8e3439ae4089ac27e542ff8f9e64a7aa093d67 Author: Iain Buclaw <ibuclaw@gdcproject.org> Date: Sun Dec 11 19:08:01 2022 +0100 d: Remove "final" and "override" from visitor method. This was added by the backport of an ICE in r12-8969. While harmless, it was not until r13-758 that "final" and "override" were introduced to all visitor methods in the D front-end. Removing it from the release branch just for consistency with the rest of the file. gcc/d/ChangeLog: * imports.cc (ImportVisitor::visit (OverloadSet *)): Remove "final" and "override" from visitor method. Diff: --- gcc/d/imports.cc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gcc/d/imports.cc b/gcc/d/imports.cc index 4ce6f026b29..dfda2401ee8 100644 --- a/gcc/d/imports.cc +++ b/gcc/d/imports.cc @@ -161,7 +161,7 @@ public: } /* Build IMPORTED_DECLs for all overloads in a set. */ - void visit (OverloadSet *d) final override + void visit (OverloadSet *d) { vec<tree, va_gc> *tset = NULL;
reply other threads:[~2022-12-11 18:14 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=20221211181417.1D6F43832E57@sourceware.org \ --to=ibuclaw@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).