220 11305 <5ff6c439-3147-4d5f-809a-8adf86c17dc4@isocpp.org> article Path: news.gmane.org!not-for-mail From: Jeremy Maitin-Shepard Newsgroups: gmane.comp.lang.c++.isocpp.proposals Subject: Re: Comments on n3976 (array_view) Date: Fri, 13 Jun 2014 15:07:27 -0700 (PDT) Lines: 81 Approved: news@gmane.org Message-ID: <5ff6c439-3147-4d5f-809a-8adf86c17dc4@isocpp.org> References: <7177de96-50e1-4590-99dc-eda255203f26@isocpp.org> Reply-To: std-proposals@isocpp.org NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_185_10928948.1402697247860" X-Trace: ger.gmane.org 1402697256 6732 80.91.229.3 (13 Jun 2014 22:07:36 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 13 Jun 2014 22:07:36 +0000 (UTC) To: std-proposals@isocpp.org Original-X-From: std-proposals+bncBCYZZ4E5WQCRBIPM5WOAKGQE24K75YI@isocpp.org Sat Jun 14 00:07:31 2014 Return-path: Envelope-to: gclcip-std-proposals@m.gmane.org Original-Received: from mail-ob0-f198.google.com ([209.85.214.198]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1WvZdC-00007R-PH for gclcip-std-proposals@m.gmane.org; Sat, 14 Jun 2014 00:07:31 +0200 Original-Received: by mail-ob0-f198.google.com with SMTP id uy5sf15685644obc.9 for ; Fri, 13 Jun 2014 15:07:29 -0700 (PDT) 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: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=6QpM5JIygxDctfdqFTn4VJvPp7AH94oTDL5QB2YM/Dk=; b=UIp9kYi6pImFkSsoP46udRSy/TKUtaeb1ffBojaWumZVqVGOPr2EUwhkBzD+uOI3Cv KXiJlz5Nx2CD4VSb5E+aBNR4UhAF0QDkfda2sVJrTxv7hnyY6iyuIbkWAOiMplFJHwIC wzorSGCFoQ0GCM+Tiu+8lGyjpL/S1ejgkcv+H4+0oTj5piV5sE9z/xXLeGAjTjvMoFva gojVoA06QV9NWZFTwPKiwPm9K9i8FdNqtbJeiYKDrus9yAAk9w1PYbbsmYmqxoZMjNDD gJAhOWN/AZ58WlvAwjPBM20DiA/WxywrpeDrYN2kVd7ML3Pk2acoh3jFIA8yrt4rVIFx Uung== X-Gm-Message-State: ALoCoQlHcX/okTuXQ10j1KGliLkcmV0HN2WjL+eB2gWPk+b0v74t3CaP6T0yvloOK5+K4Cexp1Px X-Received: by 10.182.249.115 with SMTP id yt19mr1339667obc.25.1402697249891; Fri, 13 Jun 2014 15:07:29 -0700 (PDT) X-BeenThere: std-proposals@isocpp.org Original-Received: by 10.50.12.102 with SMTP id x6ls386018igb.22.gmail; Fri, 13 Jun 2014 15:07:29 -0700 (PDT) X-Received: by 10.50.73.196 with SMTP id n4mr142228igv.14.1402697249212; Fri, 13 Jun 2014 15:07:29 -0700 (PDT) In-Reply-To: <7177de96-50e1-4590-99dc-eda255203f26@isocpp.org> X-Original-Sender: jeremy@jeremyms.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:11305 Archived-At: ------=_Part_185_10928948.1402697247860 Content-Type: text/plain; charset=UTF-8 On Friday, June 13, 2014 2:37:50 PM UTC-7, Sean Middleditch wrote: > > On Friday, June 13, 2014 12:17:40 PM UTC-7, Jeremy Maitin-Shepard wrote: >> >> C++ is sorely in need of a "vocabulary type" for representing pointer >> ranges. >> > > There's already a Ranges sub group working on this problem, and looking at > even more general cases of ranges than just pairs of iterators/pointers. > > http://www.open-std.org/mailman/listinfo/ranges > Sure, but (pointer, size) ranges are an extremely common and important case, and devising a comprehensive range library that handles all cases is much harder than handling just the (pointer, size) case. Also, in the worst case, a one-dimensional array_view type would become redundant after a range library is standardized, but it wouldn't cause any interoperability problems, since the types would surely be implicitly convertible. -- --- 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_185_10928948.1402697247860 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Friday, June 13, 2014 2:37:50 PM UTC-7, Sean Mi= ddleditch wrote:
On Friday, June 13, 2014 12:17:40 PM UTC-7, Jeremy Maitin-Shepard wrote:=
C++ is sorely in n= eed of a "vocabulary type" for representing pointer ranges.

There's already a Ranges sub group working on th= is problem, and looking at even more general cases of ranges than just pair= s of iterators/pointers.


Sure, but (pointer, size) ranges are an extremely common and im= portant case, and devising a comprehensive range library that handles all c= ases is much harder than handling just the (pointer, size) case.  Also= , in the worst case, a one-dimensional array_view type would become redunda= nt after a range library is standardized, but it wouldn't cause any interop= erability problems, since the types would surely be implicitly convertible.=

--

---
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_185_10928948.1402697247860-- .