220 13629 <45b04755-e230-435b-93c1-3aecbd6a7149@isocpp.org> article Path: news.gmane.org!not-for-mail From: Matthew Fioravante Newsgroups: gmane.comp.lang.c++.isocpp.proposals Subject: Re: The view concept Date: Fri, 3 Oct 2014 11:16:54 -0700 (PDT) Lines: 71 Approved: news@gmane.org Message-ID: <45b04755-e230-435b-93c1-3aecbd6a7149@isocpp.org> References: <428c47bd-67f2-47d1-98c0-e5ca85698076@isocpp.org> Reply-To: std-proposals@isocpp.org NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_5_580271815.1412360214196" X-Trace: ger.gmane.org 1412360226 4258 80.91.229.3 (3 Oct 2014 18:17:06 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 3 Oct 2014 18:17:06 +0000 (UTC) Cc: mw_triad@users.sourceforge.net To: std-proposals@isocpp.org Original-X-From: std-proposals+bncBDELF54RTIGRBFWQXOQQKGQEIEVPD3A@isocpp.org Fri Oct 03 20:17:00 2014 Return-path: Envelope-to: gclcip-std-proposals@m.gmane.org Original-Received: from mail-pd0-f200.google.com ([209.85.192.200]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Xa7PU-0006Qw-6m for gclcip-std-proposals@m.gmane.org; Fri, 03 Oct 2014 20:16:56 +0200 Original-Received: by mail-pd0-f200.google.com with SMTP id ft15sf129899pdb.7 for ; Fri, 03 Oct 2014 11:16:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:message-id:in-reply-to:references:subject :mime-version:x-original-sender:reply-to:precedence:mailing-list :list-id:list-post:list-help:list-archive:list-subscribe :list-unsubscribe:content-type; bh=B92Q49GmoxxJrKc82rqknc3nniT97mXybn3un+JTEX8=; b=T2wRemA21pozodN2qGKGv1BUqaPaY/IsfqHUBvWKUw0R3Y6Quj0PWRFZ1bu2NESAG+ PmES8strmcvfpiu38WrEex5xW1Cr0dmehBeeZQbb1tL/ud4EvhBMMPdf2cCiTSrAFhjN lv43TbxnfEIWVOaJsQC4YKQOO+h5s5KH+WgzNBhRF63yP4TEwW2AUgHUI9BT3GK3Yikk rc0mf8/dkpsKrhxP361538AeHMPnR5BL41Tan0LP/nw7asozh/GPMVqvJuzZ0AqTDhmY txUbT4Glr4oirLnyug/IqO2VaRVqvIR0HObsGOtnyhaqsxPQBuxvr6Td2rStVLSlA65G PBMA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:message-id:in-reply-to :references:subject:mime-version:x-original-sender:reply-to :precedence:mailing-list:list-id:list-post:list-help:list-archive :list-subscribe:list-unsubscribe:content-type; bh=B92Q49GmoxxJrKc82rqknc3nniT97mXybn3un+JTEX8=; b=VRfM2csfoLc9ECKv+MrV0YQGgcnRZxxWqxmLzBSi+Q4TmpZ+POGB+2M2wEuyewZuch lMVELBtO7+mfKOhtl3eDbngojl8Rs0JBSuEHTl+xosIgsjJbbnqiRxxoKbTYpRveZLyL M/uPgUDXO9nA6SS4sI0qpwsw0JextdVm02CZ9lU/yDCz5p4bL2RlcGFKoBvFQ3adV+/7 ywBoAtiJjJevjlw+7AiWU32haHPrHD7se4XFEe3ICynRRby1yCZjw1vOVRA3OxxOKHea LNg1/JEEAuFFlSMw021hDgqrSgWWRzWAAhkJMl+3Ou6ZAfYPhWGvOcyrmxe8/yA5mYZc 7BCA== X-Gm-Message-State: ALoCoQmvCE+LaWbKj9Dzxz7EbASE0T4zNfYH/XIYdHsd37UXup43Sa2QoBX0Ih84HgoMSrJuOlss X-Received: by 10.70.37.72 with SMTP id w8mr1882327pdj.0.1412360215097; Fri, 03 Oct 2014 11:16:55 -0700 (PDT) X-BeenThere: std-proposals@isocpp.org Original-Received: by 10.140.95.12 with SMTP id h12ls1244072qge.43.gmail; Fri, 03 Oct 2014 11:16:54 -0700 (PDT) X-Received: by 10.140.20.39 with SMTP id 36mr26797qgi.15.1412360214498; Fri, 03 Oct 2014 11:16:54 -0700 (PDT) In-Reply-To: X-Original-Sender: fmatthew5876@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:13629 Archived-At: ------=_Part_5_580271815.1412360214196 Content-Type: text/plain; charset=UTF-8 On Friday, October 3, 2014 2:13:26 PM UTC-4, Matthew Woehlke wrote: > > > std::copy? Given that one of the ideas of a "view" is to be agnostic as > to the underlying storage (e.g. raw array, std::array, std::vector, > etc.), it may or may not make sense to have anything "more direct". > > It may make sense to copy data from one view into another, but to me > that feels like std::copy is the correct tool. > > This could work. When you do a std::copy(), you are conceptually converting the src and dest views into ranges, and then invoking the copy algorithm. Still, it might be nice to have a built in copy mechanism. For 2 pointers, you can dereference them and call op=(). Views don't have any built-in convenience mechanism. -- --- 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/. ------=_Part_5_580271815.1412360214196 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Friday, October 3, 2014 2:13:26 PM UTC-4, Matth= ew Woehlke wrote:

std::copy= ? Given that one of the ideas of a "view" is to be agnostic as
to the underlying storage (e.g. raw array, std::array, std::vector,
etc.), it may or may not make sense to have anything "more direct".

It may make sense to copy data from one view into another, but to me
that feels like std::copy is the correct tool.


This could work. When you do a std::copy(), you a= re conceptually converting the src and dest views into ranges, and then inv= oking the copy algorithm.

Still, it might be nice to have a built i= n copy mechanism.

For 2 pointers, you can dereference them and call = op=3D(). Views don't have any built-in convenience mechanism.

--

---
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-proposa= ls+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>.
------=_Part_5_580271815.1412360214196-- .