W3C home > Mailing lists > Public > public-script-coord@w3.org > July to September 2014

Re: Promise<void> or Promise<undefined>?, was Re: RfC: pre-LC version of Screen Orientation; deadline August 18

From: Marcos Caceres <marcos@marcosc.com>
Date: Thu, 14 Aug 2014 19:33:07 -0400
To: Jonas Sicking <jonas@sicking.cc>
Cc: Dominique Hazael-Massieux <dom@w3.org>, Domenic Denicola <domenic@domenicdenicola.com>, public-script-coord <public-script-coord@w3.org>, Mounir Lamouri <mounir@lamouri.fr>
Message-ID: <etPan.53ed4733.216231b.e7a@Marcoss-MacBook-Pro.local>


On August 14, 2014 at 7:31:05 PM, Jonas Sicking (jonas@sicking.cc) wrote:
> On Thu, Aug 14, 2014 at 1:36 PM, Marcos Caceres wrote:
> > interface ScreenOrientation {
> > Promise lock (OrientationLockType orientation);
> > }
>  
> It doesn't make sense to put a *value* between the <>. You should put
> a *type* there. I.e. it doesn't make sense to do
>  
> Promise<1> returnOne();
>  
> The thing you do is
>  
> Promise returnOne();
>  
> 'void' is the type for 'nothing', so that's what should be used for
> functions that only return undefined. Whether they return that
> synchronously or asynchronously.

Yeah, agree. The confusion was "undefined" being treated as a type (not at a value).  
Received on Thursday, 14 August 2014 23:33:35 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:22 UTC