220 5027 article Path: news.gmane.org!not-for-mail From: Ville Voutilainen Newsgroups: gmane.comp.lang.c++.isocpp.proposals Subject: Re: Require that this should be always caputred by copy. Date: Thu, 13 Jun 2013 23:53:46 +0300 Lines: 85 Approved: news@gmane.org Message-ID: References: <51bf2631-aed7-4433-b16d-15ee15e87f29@isocpp.org> Reply-To: std-proposals@isocpp.org NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=f46d0446325298671d04df0f53b8 X-Trace: ger.gmane.org 1371156828 4792 80.91.229.3 (13 Jun 2013 20:53:48 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 13 Jun 2013 20:53:48 +0000 (UTC) To: std-proposals@isocpp.org Original-X-From: std-proposals+bncBC5JHI7A7ALRBW7C5CGQKGQEJF23B5Q@isocpp.org Thu Jun 13 22:53:49 2013 Return-path: Envelope-to: gclcip-std-proposals@m.gmane.org Original-Received: from mail-qc0-f200.google.com ([209.85.216.200]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1UnEWi-0008HJ-Ta for gclcip-std-proposals@m.gmane.org; Thu, 13 Jun 2013 22:53:49 +0200 Original-Received: by mail-qc0-f200.google.com with SMTP id n1sf4837929qcx.11 for ; Thu, 13 Jun 2013 13:53:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-beenthere:mime-version:in-reply-to:references:date:message-id :subject:from:to:x-original-sender:x-original-authentication-results :reply-to:precedence:mailing-list:list-id:x-google-group-id :list-post:list-help:list-archive:list-subscribe:list-unsubscribe :content-type; bh=rlCzsIF594HMyuWplayShbC4TN6GC29vpiDrWcQ9KSo=; b=nkeVGED8MNAxrF47Lw4b1Z7ac4RdexrN9gUemlRV1y7W21Bfpc0GvuEl9rDRSF3czo kFaFbXixHYtQnNPBXGJ9UjOH89rmK4d6GUCSKjH4KrRMl6Mm+znmKSptqupNi8YDAxJs kyT40n0boI+1M9cwFX8ILxuNI+CnhQr2DZe8YJcQ7bravWWo3T2UZ3wMivEMaqZ4aT/7 /hOmdx6hEwA9tkbmrzBqy6ZMdVyMLgqHDDOvysONFM+Ad9lY8d+6CgpQWTUnOzs1adas wQ6ocVC4GqGkDwhD0itdrgH+2X/9o1Q/1b37wUt3ktT3SrO4wxtoj9fmzsnp9p87IFkS 4qmQ== X-Received: by 10.224.86.200 with SMTP id t8mr2296854qal.0.1371156828089; Thu, 13 Jun 2013 13:53:48 -0700 (PDT) X-BeenThere: std-proposals@isocpp.org Original-Received: by 10.49.81.243 with SMTP id d19ls1157633qey.2.gmail; Thu, 13 Jun 2013 13:53:46 -0700 (PDT) X-Received: by 10.49.75.73 with SMTP id a9mr3725620qew.30.1371156826969; Thu, 13 Jun 2013 13:53:46 -0700 (PDT) Original-Received: from mail-qc0-x22a.google.com (mail-qc0-x22a.google.com [2607:f8b0:400d:c01::22a]) by mx.google.com with ESMTPS id m6si6029009qao.84.2013.06.13.13.53.46 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 13 Jun 2013 13:53:46 -0700 (PDT) Received-SPF: pass (google.com: domain of ville.voutilainen@gmail.com designates 2607:f8b0:400d:c01::22a as permitted sender) client-ip=2607:f8b0:400d:c01::22a; Original-Received: by mail-qc0-f170.google.com with SMTP id s1so3447100qcw.15 for ; Thu, 13 Jun 2013 13:53:46 -0700 (PDT) X-Received: by 10.229.157.195 with SMTP id c3mr236626qcx.88.1371156826777; Thu, 13 Jun 2013 13:53:46 -0700 (PDT) Original-Received: by 10.224.174.143 with HTTP; Thu, 13 Jun 2013 13:53:46 -0700 (PDT) In-Reply-To: X-Original-Sender: ville.voutilainen@gmail.com X-Original-Authentication-Results: mx.google.com; spf=pass (google.com: domain of ville.voutilainen@gmail.com designates 2607:f8b0:400d:c01::22a as permitted sender) smtp.mail=ville.voutilainen@gmail.com; dkim=pass header.i=@gmail.com Precedence: list Mailing-list: list std-proposals@isocpp.org; contact std-proposals+owners@isocpp.org List-ID: X-Google-Group-Id: 399137483710 List-Post: , List-Help: , List-Archive: List-Subscribe: , List-Unsubscribe: , Xref: news.gmane.org gmane.comp.lang.c++.isocpp.proposals:5027 Archived-At: --f46d0446325298671d04df0f53b8 Content-Type: text/plain; charset=ISO-8859-1 On 13 June 2013 23:49, Nevin Liber wrote: > On 13 June 2013 15:16, wrote: > >> Currently the standard (C++14 CD - NS3690) disallows explicit capture of >> this by reference the this seems to be allowed to be captured implicit by >> reference by the [&]. $5.1.2: >> > > Is this something that can be handled editorially? > > Does it matter? Is there a use case that can distinguish between > capturing this by reference and this by value? > > And if there is such a use case, is it not covered by using an init-capture? Hmm. [&foo = this] doesn't work, we can't initialize a ref-to-nonconst from a prvalue, and this is a prvalue... -- --- You received this message because you are subscribed to the Google Groups "ISO C++ Standard - Future Proposals" group. To unsubscribe from this group and stop receiving emails from it, send an email to std-proposals+unsubscribe@isocpp.org. To post to this group, send email to std-proposals@isocpp.org. Visit this group at http://groups.google.com/a/isocpp.org/group/std-proposals/. --f46d0446325298671d04df0f53b8 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable



On 13 June 2013 23:49, Nevin Liber <nevin@eviloverlord.com> wrote:
On 13 June 2013 15:16, <tomaszkam@gmail.com> wrote:
Currently the standard (C++14 CD - NS3690) disallows explicit capture of th= is by reference the this seems to be allowed to be captured implicit by ref= erence by the [&]. $5.1.2:

Is this somet= hing that can be handled editorially?

Does it matter?=A0 Is there a use case that can distinguish between cap= turing this by reference and this by value?


And if there is such a use c= ase, is it not covered by using an init-capture?

=
Hmm. [&foo =3D this] doesn't work, we ca= n't initialize a ref-to-nonconst from a prvalue, and this is a prvalue.= ...

--
 
---
You received this message because you are subscribed to the Google Groups &= quot;ISO C++ Standard - Future Proposals" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to std-proposals+unsubscribe@isocpp.org.
To post to this group, send email to std-proposals@isocpp.org.
Visit this group at http://groups.google.com/a/isocpp.org/group/std-proposals/<= /a>.
 
 
--f46d0446325298671d04df0f53b8-- .