220 4837 <79a2d3b8-5ab0-48e0-a200-32185c38f9c3@isocpp.org> article Path: news.gmane.org!not-for-mail From: Alex B Newsgroups: gmane.comp.lang.c++.isocpp.proposals Subject: Re: Re: Proposal: std::sequence Date: Mon, 3 Jun 2013 13:41:18 -0700 (PDT) Lines: 61 Approved: news@gmane.org Message-ID: <79a2d3b8-5ab0-48e0-a200-32185c38f9c3@isocpp.org> 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="----=_Part_721_8046597.1370292078688" X-Trace: ger.gmane.org 1370292082 12952 80.91.229.3 (3 Jun 2013 20:41:22 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 3 Jun 2013 20:41:22 +0000 (UTC) To: std-proposals@isocpp.org Original-X-From: std-proposals+bncBC7JZJ43WYOBB376WOGQKGQE3H24JFI@isocpp.org Mon Jun 03 22:41:23 2013 Return-path: Envelope-to: gclcip-std-proposals@m.gmane.org Original-Received: from mail-ye0-f200.google.com ([209.85.213.200]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1UjbZB-0008QB-37 for gclcip-std-proposals@m.gmane.org; Mon, 03 Jun 2013 22:41:21 +0200 Original-Received: by mail-ye0-f200.google.com with SMTP id r2sf4266558yen.11 for ; Mon, 03 Jun 2013 13:41:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-beenthere:date:from:to:message-id:in-reply-to:references:subject :mime-version:x-original-sender:reply-to:precedence:mailing-list :list-id:x-google-group-id:list-post:list-help:list-archive :list-subscribe:list-unsubscribe:content-type; bh=OzMm7T2RqBGDEANenpiI+BSeLmwSZJpwM/Vb2RMYxPs=; b=JkzDGCI6OTPt6Tn4W58FJtI4SYoj7bzIZgq07p8aPh/tZZ2NipGzFfBbGIq5lST0QP lhtvZ3iBKqpoydrEGIfrEzuOsyLprWZvtjofW9b1BRaRtlPTwmwTH/+PGf1b0Mq48t/r 4D/dlOCiVvvSlotRQmtquQmnnrHZFoGK6446qbDQWIGxu5qEJ1xKJH4e9PfjCATBKkXb pjaHksxTRcZkrsyyFdPlsIUzqTtCaZsV4VeoOKRBsnw1p0ypaWgZok5oDyGjDPzg4OOz 2BAUvFI0vQW/PMUKHwxxfIjY+cu6d+l8FJm/T6WQSaMMF8x/84DFhPdD4vsK5e8i1D5i 1bBA== X-Received: by 10.224.59.205 with SMTP id m13mr14775118qah.7.1370292080073; Mon, 03 Jun 2013 13:41:20 -0700 (PDT) X-BeenThere: std-proposals@isocpp.org Original-Received: by 10.49.127.114 with SMTP id nf18ls2179546qeb.8.gmail; Mon, 03 Jun 2013 13:41:19 -0700 (PDT) X-Received: by 10.49.40.168 with SMTP id y8mr1817236qek.9.1370292079080; Mon, 03 Jun 2013 13:41:19 -0700 (PDT) In-Reply-To: X-Original-Sender: devalexb@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:4837 Archived-At: ------=_Part_721_8046597.1370292078688 Content-Type: text/plain; charset=ISO-8859-1 > > I do still think that we should use const iterator_range (or a > template alias to that) to represent a continuous range whose bound can't > change, > That sounds like the long term solution to me (considering it part of a broader range support) while array_ref/sequence could solve it in a much shorter term *without *getting in the way of a future iterator_range (if it ever gets added). We have had std::pair for a long time and it did not prevent generalizing (std::tuple). -- --- 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. ------=_Part_721_8046597.1370292078688 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
I do still think that we should use const iterator_range<const T*&g= t; (or a template alias to that) to represent a continuous range whose boun= d can't change, 

That sound= s like the long term solution to me (considering it part of a broader range= support) while array_ref/sequence could solve it in a much shorter term without getting in the way of a future iterator_range (if it ever gets= added).

We have had std::pair for a long time and= it did not prevent generalizing (std::tuple).

--
 
---
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.
 
 
------=_Part_721_8046597.1370292078688-- .