public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "eugene at hutorny dot in.ua" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/64073] New: Explicit duplicate template instantiation not reported as error when using 'using' Date: Tue, 25 Nov 2014 19:37:00 -0000 [thread overview] Message-ID: <bug-64073-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64073 Bug ID: 64073 Summary: Explicit duplicate template instantiation not reported as error when using 'using' Product: gcc Version: 4.9.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: eugene at hutorny dot in.ua When derived template classes introduces a base member with using, such methods can be explicitly instantiated more than once with the same set of parameters. Please refer to attached sample
next reply other threads:[~2014-11-25 19:37 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-11-25 19:37 eugene at hutorny dot in.ua [this message] 2014-11-25 19:40 ` [Bug c++/64073] " eugene at hutorny dot in.ua 2014-12-08 18:13 ` ville.voutilainen at gmail dot com
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-64073-4@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).