220 21652 <8dd3594e-9c16-445e-8d59-fdc48530b8bf@isocpp.org> article
Path: news.gmane.org!not-for-mail
From: =?UTF-8?Q?Germ=C3=A1n_Diago?= <germandiago@gmail.com>
Newsgroups: gmane.comp.lang.c++.isocpp.proposals
Subject: Re: is await an extension of the do-notation? (was Re:
 Re: Resumable expressions p0114r0 vs async/await P0057R0)
Date: Tue, 13 Oct 2015 04:58:01 -0700 (PDT)
Lines: 73
Approved: news@gmane.org
Message-ID: <8dd3594e-9c16-445e-8d59-fdc48530b8bf@isocpp.org>
References: <639f0012-8cb4-4db3-82a6-8d042a3497f9@isocpp.org>
 <401aa118-ed0b-4c7b-92cf-3fbd706eff9d@isocpp.org>
 <fcbcc1c4-535c-4fa2-a17d-4acffe84a4b5@isocpp.org>
 <1d15dbc4-e0c1-4df1-86db-014e11f14d26@isocpp.org>
 <56114953.4030701@wanadoo.fr> <561B403D.4030403@gmail.com>
 <CAOfiQqkKvZfVatJ1Bz4qSvGc-g6iep0xeP1B1=J1-gCu43NXxg@mail.gmail.com>
 <561C07D1.3080304@gmail.com>
Reply-To: std-proposals@isocpp.org
NNTP-Posting-Host: plane.gmane.org
Mime-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_2384_570217774.1444737481264"
X-Trace: ger.gmane.org 1444737489 27641 80.91.229.3 (13 Oct 2015 11:58:09 GMT)
X-Complaints-To: usenet@ger.gmane.org
NNTP-Posting-Date: Tue, 13 Oct 2015 11:58:09 +0000 (UTC)
To: ISO C++ Standard - Future Proposals <std-proposals@isocpp.org>
Original-X-From: std-proposals+bncBDC2VXM4YYDRBSXD6OYAKGQEGL2YNZY@isocpp.org Tue Oct 13 13:58:04 2015
Return-path: <std-proposals+bncBDC2VXM4YYDRBSXD6OYAKGQEGL2YNZY@isocpp.org>
Envelope-to: gclcip-std-proposals@m.gmane.org
Original-Received: from mail-io0-f200.google.com ([209.85.223.200])
	by plane.gmane.org with esmtp (Exim 4.69)
	(envelope-from <std-proposals+bncBDC2VXM4YYDRBSXD6OYAKGQEGL2YNZY@isocpp.org>)
	id 1ZlyDT-0005Ck-Qz
	for gclcip-std-proposals@m.gmane.org; Tue, 13 Oct 2015 13:58:04 +0200
Original-Received: by iodv82 with SMTP id v82sf31692227iod.0
        for <gclcip-std-proposals@m.gmane.org>; Tue, 13 Oct 2015 04:58:03 -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
         :content-type:x-original-sender:reply-to:precedence:mailing-list
         :list-id:x-spam-checked-in-group:list-post:list-help:list-archive
         :list-subscribe:list-unsubscribe;
        bh=d4KzdYHR70FhPDlTJ2h4nGw96sgpiYmFTXZjgCpdPwY=;
        b=Z1JRYkcfuqIUBTbQ/tOTzK4v0Qj+AClB0Hla5RrOB7q1vgnm8JQc8Qye3zzE8eYjtU
         tQqPu93U9XhOO/ACnojI1t7MX3+vR4dlIaF83hdD9Mmwkp4zQjSaf4vpBCM/mBoyEflI
         hLnV2YT8jcwjoEoUfZ+GETPYXWkjldF/DtZaORSFMacWAO0OaOoZLDFQw1e3L9oGWXLu
         3r+CDLZPYYkTJ2x60rjSlfGh7gyhFo4Ne6JWymirYgVHIV23SSlVmg635z6MtRSvzbw2
         RFrnJM6dVPrfLmreEVBELNxR48pUKI6G67Zse6fjxqmvc9PyMewfV//Rtvt20nCe0yO7
         CFhg==
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:content-type:x-original-sender:reply-to
         :precedence:mailing-list:list-id:x-spam-checked-in-group:list-post
         :list-help:list-archive:list-subscribe:list-unsubscribe;
        bh=d4KzdYHR70FhPDlTJ2h4nGw96sgpiYmFTXZjgCpdPwY=;
        b=TDb6qmBP9HKhMUepwmonzndvMeWRif0X7Ms/MdMgHYsuZIF/rayR18VnhtiyW2Gl2Q
         C+1kBhhThpFJVVfp+3fGY74iWut/zxUlhEpfi0NII18he3tKlzYMUJptNIZ7fdyuZ9Er
         Qf+4akOArOdGc/8KDG9KP8orBkse18NbIVpz32NBcufOj+a2RlW9vjsvye/v+e3geHot
         WYjPeKZimeehJ4EooJIQkxgTieGB7DgBHjrwwsvBR8k72DdVXyBkKJgBjG3yLGNVNIqB
         0NMpx6KGkarZwJiiAceod6K4r695wz9lNFgid9Xh6PIyrXyE+x6gWCSVI7DqdreVdszj
         F2SA==
X-Gm-Message-State: ALoCoQlFTKZ/ZScruqCYuwUfFHNH4lam4UfsoHUOCEgA3I9nm2X8Un7dbUnb0XZkNX96dE4kY6+6
X-Received: by 10.107.165.5 with SMTP id o5mr23827489ioe.5.1444737482994;
        Tue, 13 Oct 2015 04:58:02 -0700 (PDT)
X-BeenThere: std-proposals@isocpp.org
Original-Received: by 10.107.165.76 with SMTP id o73ls407859ioe.74.gmail; Tue, 13 Oct
 2015 04:58:01 -0700 (PDT)
X-Received: by 10.50.225.70 with SMTP id ri6mr118356igc.9.1444737481949;
        Tue, 13 Oct 2015 04:58:01 -0700 (PDT)
In-Reply-To: <561C07D1.3080304@gmail.com>
X-Original-Sender: germandiago@gmail.com
Precedence: list
Mailing-list: list std-proposals@isocpp.org; contact std-proposals+owners@isocpp.org
List-ID: <std-proposals.isocpp.org>
X-Spam-Checked-In-Group: std-proposals@isocpp.org
X-Google-Group-Id: 399137483710
List-Post: <http://groups.google.com/a/isocpp.org/group/std-proposals/post>, <mailto:std-proposals@isocpp.org>
List-Help: <http://support.google.com/a/isocpp.org/bin/topic.py?topic=25838>, <mailto:std-proposals+help@isocpp.org>
List-Archive: <http://groups.google.com/a/isocpp.org/group/std-proposals/>
List-Subscribe: <http://groups.google.com/a/isocpp.org/group/std-proposals/subscribe>,
 <mailto:std-proposals+subscribe@isocpp.org>
List-Unsubscribe: <mailto:googlegroups-manage+399137483710+unsubscribe@googlegroups.com>,
 <http://groups.google.com/a/isocpp.org/group/std-proposals/subscribe>
Xref: news.gmane.org gmane.comp.lang.c++.isocpp.proposals:21652
Archived-At: <http://permalink.gmane.org/gmane.comp.lang.c++.isocpp.proposals/21652>

------=_Part_2384_570217774.1444737481264
Content-Type: multipart/alternative; 
	boundary="----=_Part_2385_1057187320.1444737481264"

------=_Part_2385_1057187320.1444737481264
Content-Type: text/plain; charset=UTF-8



> It is intrinsically non-zero overhead, due to type-erasure/allocations. 
> This fact alone is strong argument against it. 
>
> This is my main concern with the proposal: type-erasure and allocations.
Seems that there are some fancy optimizations possible, but I am not sure
why we should rely on these when there are other alternatives.
 

> While with approach based on method-state-machine - we can get both: 
> generality and performance. 
>

I agree with this. On top of that I do think you can implement everything on
top of this without polluting the core language.

 

-- 

--- 
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_2385_1057187320.1444737481264
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><blockquote class=3D"gmail_quote" style=3D"margin: 0;m=
argin-left: 0.8ex;border-left: 1px #ccc solid;padding-left: 1ex;">It is int=
rinsically non-zero overhead, due to type-erasure/allocations.=20
<br>This fact alone is strong argument against it.
<br>
<br></blockquote><div>This is my main concern with the proposal: type-erasu=
re and allocations.<br>Seems that there are some fancy optimizations possib=
le, but I am not sure<br>why we should rely on these when there are other a=
lternatives.<br>=C2=A0<br></div><blockquote class=3D"gmail_quote" style=3D"=
margin: 0;margin-left: 0.8ex;border-left: 1px #ccc solid;padding-left: 1ex;=
">While with approach based on method-state-machine - we can get both:=20
<br>generality and performance.
<br></blockquote><div><br>I agree with this. On top of that I do think you =
can implement everything on<br>top of this without polluting the core langu=
age.<br><br>=C2=A0<br></div></div>

<p></p>

-- <br />
<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 <a href=3D"mailto:std-proposals+unsubscribe@isocpp.org">std-proposa=
ls+unsubscribe@isocpp.org</a>.<br />
To post to this group, send email to <a href=3D"mailto:std-proposals@isocpp=
..org">std-proposals@isocpp.org</a>.<br />
Visit this group at <a href=3D"http://groups.google.com/a/isocpp.org/group/=
std-proposals/">http://groups.google.com/a/isocpp.org/group/std-proposals/<=
/a>.<br />

------=_Part_2385_1057187320.1444737481264--
------=_Part_2384_570217774.1444737481264--

.
