220 4857 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: Tue, 4 Jun 2013 14:03:07 -0500 Lines: 82 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> <1c991e6e-6bc3-4822-9ffd-7f2508e63974@isocpp.org> Reply-To: std-proposals@isocpp.org NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a11c2b55cc1245404de58bdf6 X-Trace: ger.gmane.org 1370372643 21583 80.91.229.3 (4 Jun 2013 19:04:03 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 4 Jun 2013 19:04:03 +0000 (UTC) To: std-proposals@isocpp.org Original-X-From: std-proposals+bncBCE35H5S6IDBBFPUXCGQKGQE7HY4O6Q@isocpp.org Tue Jun 04 21:04:03 2013 Return-path: Envelope-to: gclcip-std-proposals@m.gmane.org Original-Received: from mail-yh0-f71.google.com ([209.85.213.71]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1UjwWN-0002f0-8o for gclcip-std-proposals@m.gmane.org; Tue, 04 Jun 2013 21:03:51 +0200 Original-Received: by mail-yh0-f71.google.com with SMTP id i72sf706399yha.10 for ; Tue, 04 Jun 2013 12:03:50 -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=GoUZO962c+YOiz5GfL3mbp5px+GpJPiyO1kIqWomvWo=; b=JgICrUtqULb3BncLfRfLgApbTR4HTBpMhTR+GIIPR73M03LsezuSAVRz1D8gnIH7qm 9Elx89J6Vd+M8Ul3RuVoRVOQkdJaCagKYca+I6iCi8sUnGXbaG7Pc4T1c2TtW/kRYwIA 55Juth9fGH3WOhDntwmMxp4jbXaBmBv/p4zRMDuKjd8JPkjht8H1hinL3RAQI2r6pKsx HBLctiszf82P0kIjA/ld9k1DTZBGZjCqHaHUQsfu8lXzr/PNA7Lia4eA4I2c9atGKFR3 JqIaYFBqtvDFwEK0YfoENB9Ij4HKDFFv5ZjcIdLhw4k+MQvfzPSqY28fybf7Si/86RLc Z6Sw== X-Received: by 10.236.16.19 with SMTP id g19mr15771421yhg.42.1370372630428; Tue, 04 Jun 2013 12:03:50 -0700 (PDT) X-BeenThere: std-proposals@isocpp.org Original-Received: by 10.49.24.133 with SMTP id u5ls426185qef.3.gmail; Tue, 04 Jun 2013 12:03:49 -0700 (PDT) X-Received: by 10.224.38.133 with SMTP id b5mr24727167qae.78.1370372629219; Tue, 04 Jun 2013 12:03:49 -0700 (PDT) Original-Received: from mail-qe0-f43.google.com (mail-qe0-f43.google.com [209.85.128.43]) by mx.google.com with ESMTPS id q5si10038331qcv.22.2013.06.04.12.03.48 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 04 Jun 2013 12:03:49 -0700 (PDT) Received-SPF: pass (google.com: domain of nliber@gmail.com designates 209.85.128.43 as permitted sender) client-ip=209.85.128.43; Original-Received: by mail-qe0-f43.google.com with SMTP id k5so458204qej.16 for ; Tue, 04 Jun 2013 12:03:48 -0700 (PDT) X-Received: by 10.224.65.72 with SMTP id h8mr25095883qai.73.1370372628873; Tue, 04 Jun 2013 12:03:48 -0700 (PDT) Original-Sender: nliber@gmail.com Original-Received: by 10.49.64.165 with HTTP; Tue, 4 Jun 2013 12:03:07 -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.43 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:4857 Archived-At: --001a11c2b55cc1245404de58bdf6 Content-Type: text/plain; charset=ISO-8859-1 On 4 June 2013 13:54, Jeffrey Yasskin wrote: > > Please don't say "clearly" here. Assignability is the default in C++, > and it's quite possible that our implementations stumbled into it > without actually having a firm use case. It would take actual research > to determine that we have a real need. (I suspect we do, but my > suspicion doesn't prove anything, and I'm not currently planning to > investigate in detail.) > Other than dynarray, is there any class in the standard that is copyable but not assignable? And I'm a bit worried about dynarray, as I suspect more than a few people are going to try mostly working "destruct then placement new" abomination to get around it. Of course, I didn't think of that in Bristol, and a clean hack circumventing the issue is optional>, but I digress... -- 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. --001a11c2b55cc1245404de58bdf6 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 4 June 2013 13:54, Jeffrey Yasskin <jyasskin@google.com> wrote:

Please don't say "clearly" here. Assignability is the d= efault in C++,
and it's quite possible that our implementations stumbled into it
without actually having a firm use case. It would take actual research
to determine that we have a real need. (I suspect we do, but my
suspicion doesn't prove anything, and I'm not currently planning to=
investigate in detail.)

Other than dynarray, is th= ere any class in the standard that is copyable but not assignable?

A= nd I'm a bit worried about dynarray, as I suspect more than a few peopl= e are going to try mostly working "destruct then placement new" a= bomination to get around it.=A0 Of course, I didn't think of that in Br= istol, and a clean hack circumventing the issue is optional<dynarray<= T>>, but I digress...
--
=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.
 
 
--001a11c2b55cc1245404de58bdf6-- .