public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/94310] using constructor inheritance breaks the code
Date: Sun, 19 Apr 2020 04:44:49 +0000	[thread overview]
Message-ID: <bug-94310-4-eEd2VwgO3t@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94310-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94310

--- Comment #2 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
The difference stems from the fact that in this test:

template<typename>
struct B { };

template<typename... Types>
struct A : public B<Types>... {
    using B<Types>::B...; // #1
    using B<Types>::operator=...; // #2
};

int main() {}

when parsing B<Types> in #2 cp_parser_lookup_name finds #1, which is a
dependent USING_DECL.  strip_using_decl doesn't do anything with such a
USING_DECL, so we think that we haven't found a template name.

  parent reply	other threads:[~2020-04-19  4:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-24 19:51 [Bug c++/94310] New: " tilin97 at yandex dot ru
2020-04-18 17:20 ` [Bug c++/94310] " mpolacek at gcc dot gnu.org
2020-04-19  4:44 ` mpolacek at gcc dot gnu.org [this message]
2020-04-19 15:09 ` mpolacek at gcc dot gnu.org
2021-10-18 18:38 ` ppalka at gcc dot gnu.org
2021-12-09  5:52 ` pinskia at gcc dot gnu.org

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-94310-4-eEd2VwgO3t@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: link
Be 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).