W3C home > Mailing lists > Public > public-script-coord@w3.org > April to June 2013

[promises] Difficulties with using constructors and promises together

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Thu, 20 Jun 2013 10:20:25 -0700
Message-ID: <CAAWBYDCEj99Xjecf4TbkQ24wsdktWe_6Caajd5pjubmJmvFfkQ@mail.gmail.com>
To: "public-script-coord@w3.org" <public-script-coord@w3.org>
When we're trying to construct an object, the right idiom is to use a
constructor, rather than a factory function.  On the other hand, when
we need to return something async, the right idiom is to use a
promise.

What about when we need to construct an object async?

A few examples:
* createImageBitmap()
<http://www.whatwg.org/specs/web-apps/current-work/multipage/timers.html#images>
* TaskScheduler.add() <http://web-alarms.sysapps.org/#interface-taskscheduler>

These two demonstrate both callback and Promise-based ways of dealing
with this async object creation, and both are forced into using
factory functions.

Is this just what we'll have to do?  Whenever an object can only be
created async, we have to add an "Interface.create()" function?  Or is
there a better solution floating around somewhere that I can't see?

(We've already rejected the solution of returning a promise from the
constructor - that violates several implicit assumptions about
constructor return values.)

~TJ
Received on Thursday, 20 June 2013 17:21:12 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:37:49 UTC