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++/59766] c++1y: declaring friend function with 'auto' return type deduction is rejected with bogus reason
Date: Fri, 10 Apr 2015 19:29:00 -0000 [thread overview]
Message-ID: <bug-59766-4-xPPyvpFNGu@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59766-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59766
--- Comment #10 from Jason Merrill <jason at gcc dot gnu.org> ---
(In reply to David Krauss from comment #9)
> I didn't send it to gcc-patches. It's never been necessary for me before.
I appreciate getting direct mail about C++ patches so that I see them faster; I
didn't notice this one until today. Also feel free to ping me if I haven't
responded after a week.
I'll check this in after GCC 5 branches.
next prev parent reply other threads:[~2015-04-10 19:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-10 23:59 [Bug c++/59766] New: " mizvekov at gmail dot com
2014-01-19 10:51 ` [Bug c++/59766] " lucdanton at free dot fr
2014-01-24 11:28 ` paolo.carlini at oracle dot com
2014-01-24 11:49 ` paolo.carlini at oracle dot com
2014-06-28 22:35 ` felix at fontein dot de
2014-12-05 15:06 ` redi at gcc dot gnu.org
2015-01-23 9:32 ` potswa at mac dot com
2015-01-23 9:44 ` potswa at mac dot com
2015-04-09 5:44 ` glisse at gcc dot gnu.org
2015-04-09 19:04 ` potswa at mac dot com
2015-04-10 19:29 ` jason at gcc dot gnu.org [this message]
2015-04-14 15:30 ` jason at gcc dot gnu.org
2015-04-22 20:53 ` jason at gcc dot gnu.org
2015-04-22 20:53 ` jason at gcc dot gnu.org
2015-04-23 13:21 ` jason at gcc dot gnu.org
2015-04-23 13:23 ` 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-59766-4-xPPyvpFNGu@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).