Currently the Resolver tests that a @resolve Promise is instanceof Promise. Promises seem to be a bit fickle in that there are many different implementations and ways to get a global Promise object.
The question is should we expect one global Promise object or provide a duckpunch to interop with the different methods?
Alternatively, we could ignore Promises and use a callback which the consumer is responsible for calling in whatever async control flow implementation they should choose.
Currently the Resolver tests that a
@resolve
Promise isinstanceof Promise
. Promises seem to be a bit fickle in that there are many different implementations and ways to get a global Promise object.A few possibilities:
The question is should we expect one global Promise object or provide a duckpunch to interop with the different methods?
Alternatively, we could ignore Promises and use a callback which the consumer is responsible for calling in whatever async control flow implementation they should choose.