220 4842 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 17:37:37 -0500 Lines: 69 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=e89a8f923b36f1039404de479eb5 X-Trace: ger.gmane.org 1370299104 19771 80.91.229.3 (3 Jun 2013 22:38:24 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 3 Jun 2013 22:38:24 +0000 (UTC) To: std-proposals@isocpp.org Original-X-From: std-proposals+bncBCE35H5S6IDBBW5VWSGQKGQEWCUVJ2Y@isocpp.org Tue Jun 04 00:38:21 2013 Return-path: Envelope-to: gclcip-std-proposals@m.gmane.org Original-Received: from mail-qa0-f70.google.com ([209.85.216.70]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1UjdOO-0004vm-KN for gclcip-std-proposals@m.gmane.org; Tue, 04 Jun 2013 00:38:20 +0200 Original-Received: by mail-qa0-f70.google.com with SMTP id ii15sf5222266qab.1 for ; Mon, 03 Jun 2013 15:38:19 -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=6B/id9IeeWQW54T2c+H18ESk6pKcytgOoLmR23i+Yrw=; b=hu5KZlJa4xUTYJR+11ZkM4Z/UEjPwcvbxxYepme2IPMpbKjChk69NyOSrBfU2Gs5zw cvu2Kdt76XsVsvSrVzT9abQ3/7AKpwmM0nKtLZWu4pkSTt2QXat8We7vUHXoK5gJJIgt SpTOJPklDVJEctQYt6E082N1v8Ucd9j65UQ2exLz/MnIs1TUNizPkeX4TjtvMtbLuKaU ysbN6esuHd+973JlRM7f9BhDGi6BHuHessOR4VS+n5f1VfdGGf0q6SEc9Eu/h2JCn8LY TAZLenoaqZ+05aKbSnWEgma0T/IV2mt2URp+lSi0BdNc/PviLnz03izNjSUG4S49SbO/ yhRA== X-Received: by 10.236.198.168 with SMTP id v28mr13370536yhn.10.1370299099658; Mon, 03 Jun 2013 15:38:19 -0700 (PDT) X-BeenThere: std-proposals@isocpp.org Original-Received: by 10.49.82.110 with SMTP id h14ls2312961qey.88.gmail; Mon, 03 Jun 2013 15:38:17 -0700 (PDT) X-Received: by 10.49.107.2 with SMTP id gy2mr24240927qeb.21.1370299097647; Mon, 03 Jun 2013 15:38:17 -0700 (PDT) Original-Received: from mail-qa0-x230.google.com (mail-qa0-x230.google.com [2607:f8b0:400d:c00::230]) by mx.google.com with ESMTPS id bq4si3372118qcb.148.2013.06.03.15.38.17 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 03 Jun 2013 15:38:17 -0700 (PDT) Received-SPF: pass (google.com: domain of nliber@gmail.com designates 2607:f8b0:400d:c00::230 as permitted sender) client-ip=2607:f8b0:400d:c00::230; Original-Received: by mail-qa0-f48.google.com with SMTP id f14so135012qak.7 for ; Mon, 03 Jun 2013 15:38:17 -0700 (PDT) X-Received: by 10.224.7.195 with SMTP id e3mr21138725qae.5.1370299097478; Mon, 03 Jun 2013 15:38:17 -0700 (PDT) Original-Sender: nliber@gmail.com Original-Received: by 10.49.64.165 with HTTP; Mon, 3 Jun 2013 15:37:37 -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 2607:f8b0:400d:c00::230 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:4842 Archived-At: --e89a8f923b36f1039404de479eb5 Content-Type: text/plain; charset=ISO-8859-1 On 3 June 2013 17:32, Nicol Bolas wrote: > > I agree with your general sentiment, just not the example code you give. > The idea of storing a short-term array_ref/etc in a long-term object like a > `map` is... disconcerting. > How is that any different than storing a pointer? If you need reference semantics, you shouldn't have to go through hoops just to get them, because those hoops are going to be far worse (calling deleters/placement new, using optional, etc.). -- 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. --e89a8f923b36f1039404de479eb5 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 3 June 2013 17:32, Nicol Bolas <jmckesson@gmail.com> wr= ote:

I agree with your general sentiment, just not the example code you= give. The idea of storing a short-term array_ref/etc in a long-term object= like a `map` is... disconcerting.

How is th= at any different than storing a pointer?

If you need reference semantics, you shouldn't have to go through h= oops just to get them, because those hoops are going to be far worse (calli= ng deleters/placement new, using optional, etc.).
--
=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.
 
 
--e89a8f923b36f1039404de479eb5-- .