public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/65906] using-declaration allowed for non-direct base class Date: Tue, 27 Jul 2021 21:30:00 +0000 [thread overview] Message-ID: <bug-65906-4-KNQczzBCGl@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65906-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65906 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED Target Milestone|--- |7.0 --- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> --- This was fixed with r7-4255: Implement P0136R1, Rewording inheriting constructors. Which makes sense.
prev parent reply other threads:[~2021-07-27 21:30 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-04-27 14:32 [Bug c++/65906] New: " danregister at poczta dot fm 2015-04-27 14:37 ` [Bug c++/65906] " danregister at poczta dot fm 2015-04-27 17:32 ` redi at gcc dot gnu.org 2021-07-27 21:30 ` pinskia 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-65906-4-KNQczzBCGl@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).