public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/51501] decltype over-agressive SFINAE
Date: Mon, 19 Dec 2011 22:09:00 -0000	[thread overview]
Message-ID: <bug-51501-4-wHLASIlW9E@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51501-4@http.gcc.gnu.org/bugzilla/>

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

Jason Merrill <jason at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |SUSPENDED

--- Comment #5 from Jason Merrill <jason at gcc dot gnu.org> 2011-12-19 22:06:03 UTC ---
The problem here is that the variadic 'list' is not in scope when the
trailing-return-type is parsed.  3.3.2 says,

The point of declaration for a name is immediately after its complete
declarator 

and the declarator includes the trailing-return-type.  And then since all the
arguments are integers, no argument-dependent lookup is done, so the call in
the trailing-return-type doesn't find the right template, and fails.

The versions of EDG and Clang that I have handy seem to reject this testcase on
the same basis.

This seems like a flaw in the standard.


  parent reply	other threads:[~2011-12-19 22:07 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-10 21:06 [Bug c++/51501] New: " dave at boostpro dot com
2011-12-10 21:22 ` [Bug c++/51501] " dave at boostpro dot com
2011-12-11 10:32 ` marc.glisse at normalesup dot org
2011-12-11 11:52 ` dave at boostpro dot com
2011-12-19 22:07 ` jason at gcc dot gnu.org
2011-12-19 22:09 ` jason at gcc dot gnu.org [this message]
2012-08-18 23:18 ` dave at boostpro dot com
2012-12-15  4:08 ` jason at gcc dot gnu.org
2014-05-07 20:20 ` [Bug c++/51501] [DR 1433] " redi at gcc dot gnu.org
2014-05-08 13:55 ` jason at gcc dot gnu.org
2014-05-08 14:02 ` ville.voutilainen at gmail dot com
2014-05-13 19:56 ` redi at gcc dot gnu.org
2014-10-09 10:01 ` redi at gcc dot gnu.org
2014-10-09 10:05 ` redi at gcc dot gnu.org
2021-12-10  7:21 ` pinskia at gcc dot gnu.org
2022-02-01 15:55 ` marxin at gcc dot gnu.org
2022-02-01 22:48 ` jason 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-51501-4-wHLASIlW9E@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).