220 4744 <51A6F02D.3080901@wanadoo.fr> article Path: news.gmane.org!not-for-mail From: "Vicente J. Botet Escriba" Newsgroups: gmane.comp.lang.c++.isocpp.proposals Subject: Re: Re: N3558 :A standardized representation of Asynchronous operations Date: Thu, 30 May 2013 08:22:37 +0200 Lines: 155 Approved: news@gmane.org Message-ID: <51A6F02D.3080901@wanadoo.fr> References: <519F9E48.7050700@wanadoo.fr> <519FB94F.7090703@wanadoo.fr> <51A0ADAE.5030908@wanadoo.fr> Reply-To: std-proposals@isocpp.org NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="------------030302040001070303020701" X-Trace: ger.gmane.org 1369894960 6145 80.91.229.3 (30 May 2013 06:22:40 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 30 May 2013 06:22:40 +0000 (UTC) To: std-proposals@isocpp.org Original-X-From: std-proposals+bncBDH67CONY4PBBLXATOGQKGQEEIECNNI@isocpp.org Thu May 30 08:22:40 2013 Return-path: Envelope-to: gclcip-std-proposals@m.gmane.org Original-Received: from mail-lb0-f197.google.com ([209.85.217.197]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1UhwFz-00084d-5i for gclcip-std-proposals@m.gmane.org; Thu, 30 May 2013 08:22:39 +0200 Original-Received: by mail-lb0-f197.google.com with SMTP id 10sf212240lbf.4 for ; Wed, 29 May 2013 23:22:38 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-beenthere:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:x-original-sender :x-original-authentication-results:reply-to:precedence:mailing-list :list-id:x-google-group-id:list-post:list-help:list-archive :list-subscribe:list-unsubscribe:content-type; bh=1yY3c6qSsQXMmM7U4FxTzTs6Q4JnFb9Zmv6ccxDOVQM=; b=B8Ty+TxpFFZrhgrF8Dh5gtTauI0S9Y0JLF2bz/CLvnIplQtFe8oMEjX31lyegQqqhZ kA3dzFkqpFAmbJuJ+Rg6H+YgAJ8byF7tPMZJmw7iOmyVWx7kj3nhpvM5MMUx8b1bgLFR 4I6RyULCcK2c9sxqPqTlpBLP9pmF7x8kVT5EZKi9rUhzikbI3wX1mU1E9qR572Yvn/oC fj1hNkL1Y9SJoo7EKeLV5kdP+89deChsnCZTILaoVNM5w1DcCB4aJd1rw9XsGKwmF5NN awvLp5EsKLhJBfB6dpH93W5w9Wg0E0x+p7P8Bzi8P71Ezx8+oJZMvryXYSgE4YDz9ex2 rh8g== X-Received: by 10.180.76.76 with SMTP id i12mr2014305wiw.6.1369894958599; Wed, 29 May 2013 23:22:38 -0700 (PDT) X-BeenThere: std-proposals@isocpp.org Original-Received: by 10.180.108.135 with SMTP id hk7ls137069wib.54.gmail; Wed, 29 May 2013 23:22:37 -0700 (PDT) X-Received: by 10.194.110.133 with SMTP id ia5mr3057665wjb.35.1369894957631; Wed, 29 May 2013 23:22:37 -0700 (PDT) Original-Received: from smtp.smtpout.orange.fr (smtp06.smtpout.orange.fr. [80.12.242.128]) by mx.google.com with ESMTP id uy3si7668693wjc.129.2013.05.29.23.22.37 for ; Wed, 29 May 2013 23:22:37 -0700 (PDT) Received-SPF: neutral (google.com: 80.12.242.128 is neither permitted nor denied by best guess record for domain of vicente.botet@wanadoo.fr) client-ip=80.12.242.128; Original-Received: from pc4.home ([2.11.193.225]) by mwinf5d41 with ME id i6Nd1l0024sEqES036NdoJ; Thu, 30 May 2013 08:22:37 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 In-Reply-To: <51A0ADAE.5030908@wanadoo.fr> X-Original-Sender: vicente.botet@wanadoo.fr X-Original-Authentication-Results: mx.google.com; spf=neutral (google.com: 80.12.242.128 is neither permitted nor denied by best guess record for domain of vicente.botet@wanadoo.fr) smtp.mail=vicente.botet@wanadoo.fr 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:4744 Archived-At: This is a multi-part message in MIME format. --------------030302040001070303020701 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Le 25/05/13 14:25, Vicente J. Botet Escriba a =E9crit : > Le 24/05/13 22:24, Nevin Liber a =E9crit : >> On 24 May 2013 14:02, Vicente J. Botet Escriba=20 >> > wrote: >> >> >> Returning future>>> would provide >> efficiency and safety. >> >> >> If you are going to go this route, please don't use pair. It is much=20 >> better to have field names that mean something. > > I agree that using accessors would be more readable, hide the=20 > representation and in addition it could provide a value function that=20 > would retrieve the first value set. The quiz would be to find a name=20 > for the class providing these accessors ;-) Any suggestion is welcome. > > template > class ??? > { > public: > vector vector() && noexcept; > R value() &; > }; > > auto f =3D when_any(f1, f2); > ... > int i =3D f.get().value(); // efficiency > vector v =3D f.get().vector(); // safety > > The following is safe as the futures are transfered to the new variable > auto f =3D when_any(f1, f2).to_vector(); > > But should the following compile > int i =3D when_any(f1, f2).value(); > > With the following declaration the preceding statement must fail at=20 > compile time, isn't it? > R value() &; > > Any comments from the authors? Vicente --=20 ---=20 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 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-proposa= ls/?hl=3Den. --------------030302040001070303020701 Content-Type: text/html; charset=ISO-8859-1
Le 25/05/13 14:25, Vicente J. Botet Escriba a écrit :
Le 24/05/13 22:24, Nevin Liber a écrit :
On 24 May 2013 14:02, Vicente J. Botet Escriba <vicente.botet@wanadoo.fr> wrote:

Returning future<pair<size_t, vector<future<R>>>> would provide efficiency and safety.

If you are going to go this route, please don't use pair.  It is much better to have field names that mean something.

I agree that using accessors would be more readable, hide the representation and in addition it could provide a value function that would retrieve the first value set. The quiz would be to find a name for the class providing these accessors ;-)  Any suggestion is welcome.

template <typename R>
class ???
{
public:
  vector<future<R> vector() && noexcept;
  R value() &;
};

auto f = when_any(f1, f2);
...
int i = f.get().value(); // efficiency
vector<future<R> v = f.get().vector(); // safety

The following is safe as the futures are transfered to the new variable
  auto f = when_any(f1, f2).to_vector();

But should the following compile
  int i = when_any(f1, f2).value();

With the following declaration the preceding statement must fail at compile time, isn't it?
  R value() &;


Any comments from the authors?

Vicente

--
 
---
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.
 
 
--------------030302040001070303020701-- .