From: leon zadorin <leonleon77@gmail.com>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: C++ expected-to-fail compilation goes through by not detecting mutable-specifier on lambda...
Date: Wed, 04 Mar 2020 01:54:00 -0000 [thread overview]
Message-ID: <CAPpySAYi=Cfrqvf4J9RZx4X6p3uPCjzfrtET_9r+-aT6u0=B7w@mail.gmail.com> (raw)
In-Reply-To: <CAH6eHdS+7gY-+0Gt04+6eQxm6eVQe7YzKsc=zomWU+u4ww+Lqg@mail.gmail.com>
On Tue, Mar 3, 2020 at 9:57 PM Jonathan Wakely <jwakely.gcc@gmail.com>
wrote:
> What they're doing seems kinda OK, but I think it's not actually
> allowed by the standard. The wording does say that unless the lambda
> uses the mutable keyword, the function call operator is
> const-qualified.
>
> So I think this is a bug.
Thanks Jonathan, yep makes sense. I've filed a bug report just in case:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94025
prev parent reply other threads:[~2020-03-04 1:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-02 2:57 leon zadorin
2020-03-02 3:55 ` leon zadorin
2020-03-03 10:57 ` Jonathan Wakely
2020-03-04 1:54 ` leon zadorin [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='CAPpySAYi=Cfrqvf4J9RZx4X6p3uPCjzfrtET_9r+-aT6u0=B7w@mail.gmail.com' \
--to=leonleon77@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
/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).