public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "paolo.carlini at oracle dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/52114] SFINAE out the rvalue iostream operators to give better error messages Date: Sat, 04 Feb 2012 20:33:00 -0000 [thread overview] Message-ID: <bug-52114-4-Wcq3IyLLty@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-52114-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52114 Paolo Carlini <paolo.carlini at oracle dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |daniel.kruegler at | |googlemail dot com --- Comment #2 from Paolo Carlini <paolo.carlini at oracle dot com> 2012-02-04 20:32:31 UTC --- Indeed and easy to do. Yesterday I was wondering: is there something in C++11 saying explicitly that these tricks are allowed, or some sort of blanket statement explaining how the return type specifications are meant to be read? Adding Daniel in CC.
next prev parent reply other threads:[~2012-02-04 20:33 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-02-03 18:53 [Bug libstdc++/52114] New: " b.r.longbons at gmail dot com 2012-02-04 19:02 ` [Bug libstdc++/52114] " redi at gcc dot gnu.org 2012-02-04 20:33 ` paolo.carlini at oracle dot com [this message] 2012-02-04 20:40 ` paolo.carlini at oracle dot com 2012-02-04 21:44 ` daniel.kruegler at googlemail dot com 2012-02-04 22:37 ` b.r.longbons at gmail dot com 2012-02-04 22:49 ` paolo.carlini at oracle dot com 2012-02-04 22:53 ` redi at gcc dot gnu.org 2012-02-04 22:55 ` redi at gcc dot gnu.org 2012-02-04 22:58 ` paolo.carlini at oracle dot com 2012-02-04 23:00 ` paolo.carlini at oracle dot com 2012-02-05 11:00 ` daniel.kruegler at googlemail dot com 2012-02-05 11:11 ` paolo.carlini at oracle 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-52114-4-Wcq3IyLLty@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: linkBe 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).