public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "nathan at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/95809] GCC treats inline namespace declaration as "ambiguous"
Date: Thu, 25 Jun 2020 13:44:43 +0000	[thread overview]
Message-ID: <bug-95809-4-bYrNEQnlua@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95809-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Nathan Sidwell <nathan at gcc dot gnu.org> ---
yup, dr2061 made that ill-formed.  

p1701 (wg21.link/p1701) documents the behaviour and it appears EWG is exploring
another avenue to resolve the underlying problem 2061 was attempting to fix.

  parent reply	other threads:[~2020-06-25 13:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-22  6:43 [Bug c++/95809] New: " haoxintu at gmail dot com
2020-06-25 12:16 ` [Bug c++/95809] " redi at gcc dot gnu.org
2020-06-25 13:44 ` nathan at gcc dot gnu.org [this message]
2020-06-26  9:47 ` haoxintu at gmail dot com
2020-06-26 13:16 ` nathan at gcc dot gnu.org
2021-12-14  5:01 ` [Bug c++/95809] [DR2061]GCC " 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-95809-4-bYrNEQnlua@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).