220 4537 <c959abc7-55a0-4a6a-9b20-9752cbe63af0@isocpp.org> article
Path: news.gmane.org!not-for-mail
From: Xeo <hivemaster@hotmail.de>
Newsgroups: gmane.comp.lang.c++.isocpp.proposals
Subject: Re: N3558 :A standardized representation of
 Asynchronous operation
Date: Fri, 24 May 2013 10:57:51 -0700 (PDT)
Lines: 73
Approved: news@gmane.org
Message-ID: <c959abc7-55a0-4a6a-9b20-9752cbe63af0@isocpp.org>
References: <519F9E48.7050700@wanadoo.fr>
Reply-To: std-proposals@isocpp.org
NNTP-Posting-Host: plane.gmane.org
Mime-Version: 1.0
Content-Type: multipart/alternative; 
	boundary="----=_Part_721_28179192.1369418271199"
X-Trace: ger.gmane.org 1369418273 13347 80.91.229.3 (24 May 2013 17:57:53 GMT)
X-Complaints-To: usenet@ger.gmane.org
NNTP-Posting-Date: Fri, 24 May 2013 17:57:53 +0000 (UTC)
To: std-proposals@isocpp.org
Original-X-From: std-proposals+bncBCCNBYNYXMJRBIGU72GAKGQEVQ6WFGI@isocpp.org Fri May 24 19:57:54 2013
Return-path: <std-proposals+bncBCCNBYNYXMJRBIGU72GAKGQEVQ6WFGI@isocpp.org>
Envelope-to: gclcip-std-proposals@m.gmane.org
Original-Received: from mail-gg0-f199.google.com ([209.85.161.199])
	by plane.gmane.org with esmtp (Exim 4.69)
	(envelope-from <std-proposals+bncBCCNBYNYXMJRBIGU72GAKGQEVQ6WFGI@isocpp.org>)
	id 1UfwFV-0005bl-Nj
	for gclcip-std-proposals@m.gmane.org; Fri, 24 May 2013 19:57:53 +0200
Original-Received: by mail-gg0-f199.google.com with SMTP id q3sf4998726gge.10
        for <gclcip-std-proposals@m.gmane.org>; Fri, 24 May 2013 10:57:52 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=google.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=Mz8pyYsPkZEe1Q5eXdZWLSWK2vV1hGsoJKel0GrbAg0=;
        b=hnuPwYToY+g8FgVH48yHDxEFhiADEQj18BDy4NimaM3DZe/dpJCyWyCmwByAqTRxkb
         uqCdooZh2ddLYR362gf4QNrSvSTo2MzIyW6kn+LTHgBHaro9pl/cXc5FkP3MvQ75E7sM
         4DjQLNYu81T4YJEdFITXj8walshSg1W7A21JHgrAl3OJduPEFHeaZuOs0SYIEOuFCLB/
         sCnTqKcYIhqtBdJC4usXE4MOz/+1nQ/gBWVMLZs2Vjlx0R2/clkpulpteQBeOWFk1uqr
         cxkCPrkFjc1KFJjwP8hcL2g+t7KNinDvCYE3mzelGCzk1XSbnndUcNxEyKLLzXJfw2dX
         BPuQ==
X-Received: by 10.236.16.19 with SMTP id g19mr8548617yhg.42.1369418272870;
        Fri, 24 May 2013 10:57:52 -0700 (PDT)
X-BeenThere: std-proposals@isocpp.org
Original-Received: by 10.49.18.195 with SMTP id y3ls2094564qed.67.gmail; Fri, 24 May
 2013 10:57:51 -0700 (PDT)
X-Received: by 10.49.72.130 with SMTP id d2mr1831682qev.42.1369418271746;
        Fri, 24 May 2013 10:57:51 -0700 (PDT)
In-Reply-To: <519F9E48.7050700@wanadoo.fr>
X-Original-Sender: hivemaster@hotmail.de
Precedence: list
Mailing-list: list std-proposals@isocpp.org; contact std-proposals+owners@isocpp.org
List-ID: <std-proposals.isocpp.org>
X-Google-Group-Id: 399137483710
List-Post: <http://groups.google.com/a/isocpp.org/group/std-proposals/post?hl=en>,
 <mailto:std-proposals@isocpp.org>
List-Help: <http://support.google.com/a/isocpp.org/bin/topic.py?hl=en&topic=25838>,
 <mailto:std-proposals+help@isocpp.org>
List-Archive: <http://groups.google.com/a/isocpp.org/group/std-proposals/?hl=en>
List-Subscribe: <http://groups.google.com/a/isocpp.org/group/std-proposals/subscribe?hl=en>,
 <mailto:std-proposals+subscribe@isocpp.org>
List-Unsubscribe: <http://groups.google.com/a/isocpp.org/group/std-proposals/subscribe?hl=en>,
 <mailto:googlegroups-manage+399137483710+unsubscribe@googlegroups.com>
Xref: news.gmane.org gmane.comp.lang.c++.isocpp.proposals:4537
Archived-At: <http://permalink.gmane.org/gmane.comp.lang.c++.isocpp.proposals/4537>

------=_Part_721_28179192.1369418271199
Content-Type: text/plain; charset=ISO-8859-1

On Friday, May 24, 2013 7:07:20 PM UTC+2, Vicente J. Botet Escriba wrote:
>
>  Hi, 
>
> What is the rationale for when_all to return future<vector<future<R>>> 
> instead of  future<vector<R>>?
>
What is the rationale for when_any to return future<vector<future<R>>> 
> instead of future<pair<size_t, R>> ? 
>

Likely, proper exception propagation for both. For `when_any`, it's also 
important that you get access to *all* passed futures, not just the one 
that finished - this way, you don't have to keep the vector around yourself.

-- 

--- 
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_28179192.1369418271199
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Friday, May 24, 2013 7:07:20 PM UTC+2, Vicente J. Botet Escriba wrote:<b=
lockquote class=3D"gmail_quote" style=3D"margin: 0;margin-left: 0.8ex;borde=
r-left: 1px #ccc solid;padding-left: 1ex;">
 =20

   =20
 =20
  <div>
    Hi, <br>
    <br>
    What is the rationale for when_all to return
    future&lt;vector&lt;future&lt;R&gt;&gt;&gt; instead of&nbsp;
    future&lt;vector&lt;R&gt;&gt;?<br></div></blockquote><blockquote class=
=3D"gmail_quote" style=3D"margin: 0;margin-left: 0.8ex;border-left: 1px #cc=
c solid;padding-left: 1ex;"><div bgcolor=3D"#FFFFFF" text=3D"#000000">
    What is the rationale for when_any to return
    future&lt;vector&lt;future&lt;R&gt;&gt;&gt; instead of
    future&lt;pair&lt;size_t, R&gt;&gt; ? <br></div></blockquote><div><br>L=
ikely, proper exception propagation for both. For `when_any`, it's also imp=
ortant that you get access to *all* passed futures, not just the one that f=
inished - this way, you don't have to keep the vector around yourself.</div=
>

<p></p>

-- <br />
&nbsp;<br />
--- <br />
You received this message because you are subscribed to the Google Groups &=
quot;ISO C++ Standard - Future Proposals&quot; group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to std-proposals+unsubscribe@isocpp.org.<br />
To post to this group, send email to std-proposals@isocpp.org.<br />
Visit this group at <a href=3D"http://groups.google.com/a/isocpp.org/group/=
std-proposals/?hl=3Den">http://groups.google.com/a/isocpp.org/group/std-pro=
posals/?hl=3Den</a>.<br />
&nbsp;<br />
&nbsp;<br />

------=_Part_721_28179192.1369418271199--

.