From 5cea9de92e8fd552d47b6d1088cf2700bf07b01a Mon Sep 17 00:00:00 2001 From: Daniel Bevenius Date: Thu, 14 May 2020 09:39:03 +0200 Subject: [PATCH] lib: update executionAsyncId/triggerAsyncId comment This commit updates the comment referring to the executionAsyncId/triggerAsyncId pair being stored in a std::stack. It looks like this was changed from std::stack to AliasedFloat64Array in Commit 83e5215a4e8438a43b9f0002b7a43e2fd2dd37a4 ("async_hooks: use typed array stack as fast path"). --- lib/internal/async_hooks.js | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/lib/internal/async_hooks.js b/lib/internal/async_hooks.js index b7a8c581cccd0b..66ea96ce9d7298 100644 --- a/lib/internal/async_hooks.js +++ b/lib/internal/async_hooks.js @@ -41,11 +41,11 @@ const { execution_async_resources, owner_symbol } = async_wrap; -// Store the pair executionAsyncId and triggerAsyncId in a std::stack on -// Environment::AsyncHooks::async_ids_stack_ tracks the resource responsible for -// the current execution stack. This is unwound as each resource exits. In the -// case of a fatal exception this stack is emptied after calling each hook's -// after() callback. +// Store the pair executionAsyncId and triggerAsyncId in a AliasedFloat64Array +// in Environment::AsyncHooks::async_ids_stack_ which tracks the resource +// responsible for the current execution stack. This is unwound as each resource +// exits. In the case of a fatal exception this stack is emptied after calling +// each hook's after() callback. const { pushAsyncContext: pushAsyncContext_, popAsyncContext: popAsyncContext_