On Thu, Nov 21, 2013 at 9:00 PM, Paolo Amadini <paolo.02....@amadzone.org>wrote:
> Though it may seem counter-intuitive, the non-native Promise.jsm has > grown better error reporting and debuggability, and maybe even better > performance (depending on whether DOM Promises are optimized for not > returning to the outer OS event loop when resolving promise chains). > > I just used the debuggability features to find a pending promise handler > that was causing a memory leak today, and I've taken screenshots: > > > https://developer.mozilla.org/Mozilla/JavaScript_code_modules/Promise.jsm/Promise#Debugging > > I hope to see a comparable or even better level of debuggability in the > native Promise implementation soon! > If the original reason for using randomized variable names for storing the promise state was the inability of the debugger to inspect closures, note that this is now implemented and closed over variables can now be inspected in the debugger when execution is paused. Cheers, Panos _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
