public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mbos at google dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/60927] Ambiguity not caught when name introduced through using-directive conflicts with previously declared entity
Date: Tue, 22 Apr 2014 22:27:00 -0000	[thread overview]
Message-ID: <bug-60927-4-Yb2kNHb6Lu@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60927-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60927

Maurice Bos <mbos at google dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mbos at google dot com

--- Comment #1 from Maurice Bos <mbos at google dot com> ---
Some interesting related test cases:

namespace N { struct A {}; }
namespace A {}
using namespace N;
A * x;
int main() {}

G++ correctly complains about ambiguity. When the two lines with 'N' are
removed, it complains that A is not a type. (As expected.)

Very similar test case:

#include <memory>
namespace N { struct A {}; }
namespace A {}
using namespace N;
std::unique_ptr<A> x; // Only this line is different.
int main() {}

G++ does not complain about ambiguity, but gives the same error as when the two
lines with 'N' are removed.


  reply	other threads:[~2014-04-22 22:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-22 21:31 [Bug c++/60927] New: " filip.roseen at gmail dot com
2014-04-22 22:27 ` mbos at google dot com [this message]
2014-12-14 14:54 ` [Bug c++/60927] " 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-60927-4-Yb2kNHb6Lu@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).