220 13613 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 05:53:44 -0700 (PDT) Lines: 75 Approved: news@gmane.org Message-ID: 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_892_325335473.1412340824507" X-Trace: ger.gmane.org 1412340835 13083 80.91.229.3 (3 Oct 2014 12:53:55 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 3 Oct 2014 12:53:55 +0000 (UTC) To: std-proposals@isocpp.org Original-X-From: std-proposals+bncBDELF54RTIGRBWNYXKQQKGQEU2EB7CQ@isocpp.org Fri Oct 03 14:53:48 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 1Xa2Ml-0003C6-SJ for gclcip-std-proposals@m.gmane.org; Fri, 03 Oct 2014 14:53:48 +0200 Original-Received: by mail-ob0-f198.google.com with SMTP id wp4sf7892191obc.5 for ; Fri, 03 Oct 2014 05:53:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=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=v3DdYpb+9Uzn8O8nSXcj7gCxwLk0LKCnCPs3WqG3T/0=; b=TN8fyR6RpitR7xkI35ae/ehZ36MvDE0W6Hnq1r+3vlPlKXx5/aL+fJI2+Nw8S6CsUt z+fYKF7rm542l4DLdXvIVo+OxW1rrMznPUOPE66FQ0UYEdBt/8T9gLzi5lh24qjPXH7w Qbgb9n+LKmSyKqz/7+Qfw3ZpOaMnDdc5TuTw0lCFOlSxkkNFt9RooQrfr4L/3djM/XtJ 9vWFogL+78wOwaJrEYB/RGItF8NoaIyifH9k/5h1Mx7OEMoim+nK+vijAxC7krI0NnvX zb7ACCYEOuBTMB8hLxIffm1z0pZcuEeerdvPDAJ0HJeXodJPdvX83rEZfxw+ny3oZR/c y/Nw== 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=v3DdYpb+9Uzn8O8nSXcj7gCxwLk0LKCnCPs3WqG3T/0=; b=dQpdD4s/2M0pr1mVNzm8JYGRroEK8FYpHHTxTprKyYerkDiaR+z6YX6lilTxvkThKV LQBJ9itzsjf3ErjquwtZO2BTkSVuAVEFeZY3IW+5cqeo0us1ekUi2RuHCFGdUAmZJ6S0 iOGl79Ugsb3MCC4ifCggWilYYiRqz+YVY8NWW5uGN5aUZ+5G9O+8o5rETCY0aN7oJZQG u9Ja+54AbFkDZv4TEUg7GIdiOdxsQYxriIVbjUWMy7P0bg1obGE/Bp/we6as3Egge5nl E5XELAsWr5emMnAiMw2drqrPug0g884Fp+Rw02BI02SALkvSDw7GytwMocXIfKN+zQ9X TkaA== X-Gm-Message-State: ALoCoQkIXcudAAUc/5o3ZLh3p7vVglLwNhTUxbAyovWtrnUyP58vq8UpnEN114as99neLyBq+BPV X-Received: by 10.43.141.212 with SMTP id jf20mr5891326icc.2.1412340825797; Fri, 03 Oct 2014 05:53:45 -0700 (PDT) X-BeenThere: std-proposals@isocpp.org Original-Received: by 10.140.90.20 with SMTP id w20ls1135843qgd.97.gmail; Fri, 03 Oct 2014 05:53:45 -0700 (PDT) X-Received: by 10.140.102.130 with SMTP id w2mr15636qge.16.1412340825171; Fri, 03 Oct 2014 05:53:45 -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:13613 Archived-At: ------=_Part_892_325335473.1412340824507 Content-Type: text/plain; charset=UTF-8 On Friday, October 3, 2014 2:56:47 AM UTC-4, Nicola Gigante wrote: > > > > I like the idea to set in stone those definitions. > First question, why is the memory block necessary contiguous > for all kinds of view? > I'm restricting myself to contiguous views on purpose. The more generic concept is a range and there's already a study group for that. vectors and arrays are critical for performance so this concept is very important to me. > I think it would be reasonable to expect a bitset_view to work on top > of a strided array_view that sits on top of a contiguous buffer. > I suppose that's possible, in which case bitset_view would most definitely have to sit on top of array_view. -- --- 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_892_325335473.1412340824507 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Friday, October 3, 2014 2:56:47 AM UTC-4, Nicol= a Gigante wrote:


I like the idea to set in stone those definitions.=20
First question, why is the memory block necessary contiguous
for all kinds of view?

I'm restricting myself to contiguous v= iews on purpose. The more generic concept is a range and there's already a = study group for that. vectors and arrays are critical for performance so th= is concept is very important to me.
 
I think it would be reasonable to expect a bits= et_view to work on top
of a strided array_view that sits on top of a contiguous buffer.

I suppose that's possible, in which ca= se bitset_view would most definitely have to sit on top of array_view.
 

--

---
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_892_325335473.1412340824507-- .