v8/test
littledan 013e49f73c Change which ExceptionEvents are triggered by Promises
To make async/await catch prediction work well, this patch regularizes
the exception events sent to DevTools from various places in the Promise
lifecycle. The core is that there should be an exception event when the
rejection first starts, rather than when it is propagated.

- Several cases within Promise code which propagate errors are
  modified to not trigger a new ExceptionEvent in that case, such
  as .then on a rejected Promise and returning a rejected Promise
  from .then, as well as Promise.race and Promise.all.
- Make Promise.reject() create an ExceptionEvent, subject to catch
  prediction based on the Promise stack. This is important
  so that, e.g., if "await Promise.reject()" will trigger a new
  throw (rather than a silent rethrow of something that never
  triggered an event in the first place).

BUG=v8:5167

Review-Url: https://codereview.chromium.org/2244003003
Cr-Commit-Position: refs/heads/master@{#38847}
2016-08-24 00:20:50 +00:00
..
benchmarks
cctest Disallow 'yield' in async arrow parameter lists inside generators 2016-08-23 22:17:38 +00:00
fuzzer Cleanup: Move ParseInfo to a separate file. 2016-08-22 11:33:58 +00:00
inspector_protocol_parser_test
intl
js-perf-test
memory
message
mjsunit Change which ExceptionEvents are triggered by Promises 2016-08-24 00:20:50 +00:00
mozilla
preparser
promises-aplus
simdjs
test262 [parser] Allow duplicate __proto__ keys in patterns 2016-08-20 01:01:51 +00:00
unittests Blink-compatible serialization of RegExp objects. 2016-08-23 15:16:29 +00:00
webkit Fix mistake in status update for excessive-comma-usage 2016-08-22 14:13:26 +00:00
bot_default.gyp
bot_default.isolate
BUILD.gn
default.gyp
default.isolate
optimize_for_size.gyp
optimize_for_size.isolate
perf.gyp
perf.isolate