Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

lib: update executionAsyncId/triggerAsyncId comment #33396

Closed

Conversation

danbev
Copy link
Contributor

@danbev danbev commented May 14, 2020

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 83e5215 ("async_hooks: use typed array stack as fast path").

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • commit message follows commit guidelines

@nodejs-github-bot nodejs-github-bot added the async_hooks Issues and PRs related to the async hooks subsystem. label May 14, 2020
@danbev danbev force-pushed the async_hooks_async_ids_stack_comment branch from 6aa9cd8 to b2ecdc7 Compare May 15, 2020 04:18
@nodejs-github-bot
Copy link
Collaborator

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 83e5215 ("async_hooks: use
typed array stack as fast path").
@danbev danbev force-pushed the async_hooks_async_ids_stack_comment branch from b2ecdc7 to 5cea9de Compare May 20, 2020 06:25
@nodejs-github-bot
Copy link
Collaborator

@danbev
Copy link
Contributor Author

danbev commented May 20, 2020

Landed in ff016fb.

@danbev danbev closed this May 20, 2020
danbev added a commit that referenced this pull request May 20, 2020
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 83e5215 ("async_hooks: use
typed array stack as fast path").

PR-URL: #33396
Reviewed-By: Chengzhong Wu <[email protected]>
Reviewed-By: James M Snell <[email protected]>
@danbev danbev deleted the async_hooks_async_ids_stack_comment branch May 20, 2020 09:32
codebytere pushed a commit that referenced this pull request Jun 18, 2020
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 83e5215 ("async_hooks: use
typed array stack as fast path").

PR-URL: #33396
Reviewed-By: Chengzhong Wu <[email protected]>
Reviewed-By: James M Snell <[email protected]>
@codebytere codebytere mentioned this pull request Jun 28, 2020
codebytere pushed a commit that referenced this pull request Jul 6, 2020
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 83e5215 ("async_hooks: use
typed array stack as fast path").

PR-URL: #33396
Reviewed-By: Chengzhong Wu <[email protected]>
Reviewed-By: James M Snell <[email protected]>
@codebytere codebytere mentioned this pull request Jul 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
async_hooks Issues and PRs related to the async hooks subsystem.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants