Promises
Promises copied to clipboard
slightlyoff
DOM Promises IDL/polyfill
When I debug the example below I see that wrap() swallows the exception even in the case that no rejection handlers are registered. This is not a good thing: consider...
I just tried the implementation in Chromium 30 and Firefox Nightly and both throw an error when trying to use prototype delegation with them. Chromium throws `TypeError: DOM object constructor...
Native Promises have started landing in places (like Chrome Canary), so the polyfill shouldn't try to stomp on global.Promises so blithely.
This repo points to http://dom.spec.whatwg.org/#futures which points to https://github.com/domenic/promises-unwrapping. Assuming that was then intended path, then the polyfill is out of date wrt constructor arguments: https://github.com/domenic/promises-unwrapping/issues/22
Back in #16, we ended up talking ourselves into using varargs. After seeing varargs in practice, I am now back in the array camp. Here's the essential reason: ``` js...
Something like: ``` var readFile = Promise.nodeConvert(fs.readFile); return readFile("foo.txt", "utf-8"); ``` Q Docs: https://github.com/kriskowal/q#adapting-node Q Code: https://github.com/kriskowal/q/blob/master/q.js#L1655-L1693
Hi, I'd like to publish this Javascript file using http://www.webjars.org/. In order for users to reference your library, I need to introduce some sort of version number or tag. Is...
Given: ``` function third() { return new Future(function(future) { console.log("third"); future.resolve(); }).then(function() { console.log("third.then") }); } function second() { return new function() { console.log("second"); return third().catch(errorHandler); }; } return new...
For background and details, see http://lists.w3.org/Archives/Public/www-dom/2013JanMar/0202.html http://lists.w3.org/Archives/Public/www-dom/2013JanMar/0205.html In short, in some cases we need the ability to resolve a Future synchronously. In particular, for some APIs it's important that the...
Doing this here because the mailing lists have turned into an unfollowable mess. First, some cautionary notes: this thread will use the terms "wrapping" and "unwrapping" to refer to APIs...
