220 4840 article Path: news.gmane.org!not-for-mail From: Nevin Liber Newsgroups: gmane.comp.lang.c++.isocpp.proposals Subject: Re: Re: Proposal: std::sequence Date: Mon, 3 Jun 2013 15:49:05 -0500 Lines: 76 Approved: news@gmane.org Message-ID: References: <4551abbc-43aa-4520-a91a-f8eb25a90588@isocpp.org> <2c8e6079-9c87-425a-93e2-39251df57cd8@isocpp.org> <9f1cace3-0503-4a3c-a8ce-d7546564b3ef@isocpp.org> Reply-To: std-proposals@isocpp.org NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=20cf306f750ccdddbe04de461af6 X-Trace: ger.gmane.org 1370292589 18291 80.91.229.3 (3 Jun 2013 20:49:49 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 3 Jun 2013 20:49:49 +0000 (UTC) To: std-proposals@isocpp.org Original-X-From: std-proposals+bncBCE35H5S6IDBB2UCWSGQKGQELADDJ6A@isocpp.org Mon Jun 03 22:49:49 2013 Return-path: Envelope-to: gclcip-std-proposals@m.gmane.org Original-Received: from mail-ve0-f199.google.com ([209.85.128.199]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1UjbhL-0004Bx-Ui for gclcip-std-proposals@m.gmane.org; Mon, 03 Jun 2013 22:49:48 +0200 Original-Received: by mail-ve0-f199.google.com with SMTP id ox1sf6208191veb.10 for ; Mon, 03 Jun 2013 13:49:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-beenthere:mime-version:sender:in-reply-to:references:from:date :message-id:subject: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=12nprPw8ez+busEE2tmStecfYjxaEcr1XbHmtz/R6b4=; b=AJ9eq1FNt8oRm3eG2hOfbj5mFHKVVrUk0pG5ibKvNTPvESidiLda5Ls4cruoKtgKyS vFOK1a3WbOZQdh+U4R5K7U2dfE9pghoHdDkwZ+DETDBMVP9pYvZNspBBnDDWTZ0gVcUj U58aL1pAxH/bXecoDzcpWRxLRcNzjdu2CaEM+njiexnGiH2Zq4jMTbmBlQ9qH7Qqnkiw roy8Gn+NCK3KCvbE/3wyBYtLNuHH7CVwVm//Hj2U21xiP0gbEQGyglsdEKeCtqIFRTU/ KD5yhbvDqKRERdnRmtS+Qk0fiPoOuWX/PvadxB4gYcLnaMw3zp/VCoEnJD5KSERVdZgv JYKQ== X-Received: by 10.224.215.68 with SMTP id hd4mr783973qab.5.1370292587027; Mon, 03 Jun 2013 13:49:47 -0700 (PDT) X-BeenThere: std-proposals@isocpp.org Original-Received: by 10.49.117.134 with SMTP id ke6ls332469qeb.70.gmail; Mon, 03 Jun 2013 13:49:45 -0700 (PDT) X-Received: by 10.49.81.147 with SMTP id a19mr19254466qey.47.1370292585743; Mon, 03 Jun 2013 13:49:45 -0700 (PDT) Original-Received: from mail-qe0-f44.google.com (mail-qe0-f44.google.com [209.85.128.44]) by mx.google.com with ESMTPS id t1si19730257qcy.181.2013.06.03.13.49.45 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 03 Jun 2013 13:49:45 -0700 (PDT) Received-SPF: pass (google.com: domain of nliber@gmail.com designates 209.85.128.44 as permitted sender) client-ip=209.85.128.44; Original-Received: by mail-qe0-f44.google.com with SMTP id 6so2686904qeb.17 for ; Mon, 03 Jun 2013 13:49:45 -0700 (PDT) X-Received: by 10.224.78.193 with SMTP id m1mr20524936qak.79.1370292585617; Mon, 03 Jun 2013 13:49:45 -0700 (PDT) Original-Sender: nliber@gmail.com Original-Received: by 10.49.64.165 with HTTP; Mon, 3 Jun 2013 13:49:05 -0700 (PDT) In-Reply-To: X-Original-Sender: nevin@eviloverlord.com X-Original-Authentication-Results: mx.google.com; spf=pass (google.com: domain of nliber@gmail.com designates 209.85.128.44 as permitted sender) smtp.mail=nliber@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:4840 Archived-At: --20cf306f750ccdddbe04de461af6 Content-Type: text/plain; charset=ISO-8859-1 On 3 June 2013 15:47, Alex B wrote: > > m[1] = get_array(); >> > > That's exactly the kind of use case that might not be interpreted > properly. Some (if not most) users will wrongly assume that the elements > will be copied. > > What about: > > m[1].rebind(get_array()); > Is it any more error prone than std::reference_wrapper? -- Nevin ":-)" Liber (847) 691-1404 -- --- 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/?hl=en. --20cf306f750ccdddbe04de461af6 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 3 June 2013 15:47, Alex B <devalexb@gmail.com> wrote:

m[1] =3D get_array();

That's exactly the kind of use case th= at might not be interpreted properly. Some (if not most) users will wrongly= assume that the elements will be copied.

What abo= ut:

m[1].rebind(get_array());
=

Is it any more error prone than std::reference_wrappe= r?
--
=A0Nevin ":-)" Liber=A0 <mailto:nevin@eviloverlord.= com>=A0 (847) 691-1404

--
 
---
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-pro= posals/?hl=3Den.
 
 
--20cf306f750ccdddbe04de461af6-- .