On Tue, Jun 21, 2016 at 6:15 PM, Todd Hubers <todd.hub...@alivate.com.au> wrote: > 1. Whether you await or not, the try scope's catch callback [TSCC] should > still be captured.
Why? Async code doesn't do anything special for try/catch anywhere else in the language - what does this proposal do that's worth the added complexity beyond what just using a Promise and the await/async keywords can do? > 2. If there is no use of Promise (for coders own design reasons) the try > scope's catch callback [TSCC] should be available What uses are you thinking of, and why should this be available? ~TJ _______________________________________________ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss
