This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/51452] has_nothrow_.*constructor bugs
- From: "paolo.carlini at oracle dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 09 Dec 2011 18:37:37 +0000
- Subject: [Bug libstdc++/51452] has_nothrow_.*constructor bugs
- Auto-submitted: auto-generated
- References: <bug-51452-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51452
--- Comment #12 from Paolo Carlini <paolo.carlini at oracle dot com> 2011-12-09 18:37:37 UTC ---
Thus Daniel was wrong when he said that fixing 51295 automatically renders
correct his current implementation of the trait? I suspect there is a
misunderstanding here: we are in control of both compiler and library, thus, if
I understood Daniel correctly, there is no need to keep this issue open, as if
to force some sort of workaround on the library side. Unless we *really* decide
that we don't want to wait for the front-end to be fixed. Anyway, I'm off,
anything Daniel wants to do for his trait, it's Ok with me.