public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dacamara.cameron at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/63192] New: non-mutable lambda capture by value on reference does not apply const
Date: Fri, 05 Sep 2014 20:55:00 -0000	[thread overview]
Message-ID: <bug-63192-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63192

            Bug ID: 63192
           Summary: non-mutable lambda capture by value on reference does
                    not apply const
           Product: gcc
           Version: 4.9.0
            Status: UNCONFIRMED
          Severity: minor
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: dacamara.cameron at gmail dot com

This is an example taken directly from the standard (5.1.2.19) with a bit of
decoration for output. The last case produces false when it should be true.


int main() {
    float x, &r = x;
    std::cout<<std::boolalpha;
    [=] { // x and r are not captured (appearance in a decltype operand is not
an odr-use)
        std::cout<<std::is_same<decltype(x), float>::value<<'\n' // has type
float
        <<std::is_same<decltype((x)), float const&>::value<<'\n' // has type
float const& because this lambda
                                                                 // is not
mutable and x is an lvalue
        <<std::is_same<decltype(r), float&>::value<<'\n'         // r1 has type
float& (transformation not considered)
        <<std::is_same<decltype((r)), float const&>::value;      // r2 has type
float const&
    }();
}


             reply	other threads:[~2014-09-05 20:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-05 20:55 dacamara.cameron at gmail dot com [this message]
2014-12-13 23:36 ` [Bug c++/63192] " ville.voutilainen at gmail dot com
2014-12-13 23:40 ` ville.voutilainen at gmail dot com
2021-08-12 22:57 ` pinskia at gcc dot gnu.org
2023-11-10 16:06 ` ppalka 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-63192-4@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).