From: Jason Merrill <jason@redhat.com>
To: Adam Butcher <adam@jessamine.co.uk>
Cc: gcc-patches@gcc.gnu.org,
Gabriel Dos Reis <gdr@integrable-solutions.net>,
Andrew Sutton <andrew.n.sutton@gmail.com>
Subject: Re: [PATCH 3/3] Support dumping type bindings in lambda diagnostics.
Date: Wed, 28 Aug 2013 03:02:00 -0000 [thread overview]
Message-ID: <521D3C7F.6080907@redhat.com> (raw)
In-Reply-To: <a4bdb7cc4d3003a35e06d0b1ccb56fcd@imap.force9.net>
On 08/27/2013 02:46 PM, Adam Butcher wrote:
> Okay. As it stands, it means that you get an additional 'const' in
> diagnostics for lambda's not declared 'mutable'.
Hmm, I guess it would be preferable to use 'mutable' or nothing when
printing the lambda just like when declaring one.
Jason
next prev parent reply other threads:[~2013-08-27 23:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-11 19:50 Lambda templates and implicit function templates Adam Butcher
2013-08-11 19:50 ` [PATCH 1/3] Support lambda templates Adam Butcher
2013-08-12 15:47 ` Jason Merrill
2013-08-12 23:52 ` Adam Butcher
2013-08-13 12:29 ` Jason Merrill
2013-08-11 19:50 ` [PATCH 3/3] Support dumping type bindings in lambda diagnostics Adam Butcher
2013-08-27 16:57 ` Jason Merrill
2013-08-27 19:43 ` Adam Butcher
2013-08-28 3:02 ` Jason Merrill [this message]
2013-08-28 9:08 ` [PATCH] Support dumping type bindings and 'mutable' qualifier " Adam Butcher
2013-08-28 12:57 ` Gabriel Dos Reis
2013-08-29 15:15 ` Adam Butcher
2013-08-29 15:57 ` Gabriel Dos Reis
2013-08-29 18:24 ` Adam Butcher
2013-08-29 18:51 ` Adam Butcher
2013-08-29 19:38 ` Gabriel Dos Reis
2013-08-11 19:50 ` [PATCH 2/3] Support using 'auto' in a function parameter list to introduce an implicit template parameter Adam Butcher
2013-08-12 16:52 ` Jason Merrill
2013-08-13 0:34 ` Adam Butcher
2013-08-14 14:07 ` Jason Merrill
2013-08-14 14:29 ` Gabriel Dos Reis
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=521D3C7F.6080907@redhat.com \
--to=jason@redhat.com \
--cc=adam@jessamine.co.uk \
--cc=andrew.n.sutton@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdr@integrable-solutions.net \
/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).