summaryrefslogtreecommitdiff
path: root/deps/v8/src/ast/context-slot-cache.cc
diff options
context:
space:
mode:
authorMichaël Zasso <targos@protonmail.com>2017-03-21 16:16:48 +0100
committerMichaël Zasso <targos@protonmail.com>2017-03-25 09:44:11 +0100
commit07088e6fc1342b5581d9e6f7ce084308573e3139 (patch)
tree05df5e41276c73c3f3392e1aa0bce02084866d2b /deps/v8/src/ast/context-slot-cache.cc
parent8394b05e20d3b661bb36cf778cd1f8c323334d7d (diff)
downloadnode-new-07088e6fc1342b5581d9e6f7ce084308573e3139.tar.gz
deps: backport 39642fa from upstream V8
This is an almost clean cherry-pick of the original commit. The only conflict was related to a rename of an internal class. Original commit message: [async-await] (simpler) fix for Return in try/finally in async functions Alternative approach to https://codereview.chromium.org/2667983004/, which does not depend on implicit control flow changes from https://codereview.chromium.org/2664083002 - Remove handling for `async function` from Parser::RewriteReturn(). This functionality is moved to BytecodeGenerator::BuildAsyncReturn(). This ensures that promise resolution is deferred until all finally blocks are evaluated fully. - Add a new deferred command (CMD_ASYNC_RETURN), which instructs ControlScope to generate return code using BuildAsyncReturn rather than BuildReturn. - Parser has a new `NewReturnStatement()` helper which determines what type of return statement to generate based on the type of function. BUG=v8:5896, v8:4483 R=littledan@chromium.org, neis@chromium.org, rmcilroy@chromium.org, adamk@chromium.org, gsathya@chromium.org Review-Url: https://codereview.chromium.org/2685683002 Cr-Commit-Position: refs/heads/master@{#43104} Fixes: https://github.com/nodejs/node/issues/11960 PR-URL: https://github.com/nodejs/node/pull/11752 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Franziska Hinkelmann <franziska.hinkelmann@gmail.com>
Diffstat (limited to 'deps/v8/src/ast/context-slot-cache.cc')
0 files changed, 0 insertions, 0 deletions