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++/49266] [C++0x] Another incomplete type regression with noexcept
Date: Sat, 04 Jun 2011 23:43:00 -0000 [thread overview]
Message-ID: <bug-49266-4-DMdW10CuCV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49266-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49266
Jason Merrill <jason at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |DUPLICATE
--- Comment #2 from Jason Merrill <jason at gcc dot gnu.org> 2011-06-04 23:42:03 UTC ---
(In reply to comment #1)
> Thanks Marc. I guess we need a definitive word here about whether these are c++
> front issues or unavoidable problems caused by the implementation of the traits
> via sfinae.
This definitely is not a front end bug.
> In the latter case we have unfortunately to be prepared to revert
> all the noexcept work involving traits until we get front-end support. Very
> sad, of course: personally, I didn't think sfinae-based techniques had serious
> limitations besides access-control. Would be something worth popularizing, can
> affect a lot of sfinae uses outside the library too, of course.
I don't think this is a sfinae vs intrinsic traits issue; intrinsic traits
would do basically the same thing. It's an issue of involving traits/sfinae in
function signatures so that we trigger more instantiations when considering a
function during overload resolution rather than later, when the function is
instantiated. The idea about deferring instantiation of exception-specifiers
seems likely to address this for noexcept specifically, but there might be
similar issues caused by increased use of sfinae for selecting between
overloads.
*** This bug has been marked as a duplicate of bug 49107 ***
prev parent reply other threads:[~2011-06-04 23:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-02 10:26 [Bug c++/49266] New: " marc.glisse at normalesup dot org
2011-06-04 12:31 ` [Bug c++/49266] " paolo.carlini at oracle dot com
2011-06-04 23:43 ` jason at gcc dot gnu.org [this message]
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-49266-4-DMdW10CuCV@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).