-
Notifications
You must be signed in to change notification settings - Fork 31.3k
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
assert: add __proto__
null
#48661
base: main
Are you sure you want to change the base?
assert: add __proto__
null
#48661
Conversation
I believe we need a benchmark CI for this since its used in lots of places in Node.js. |
you're right, Can you please trigger the benchmark CI? |
Benchmark CI: https://ci.nodejs.org/view/Node.js%20benchmark/job/benchmark-node-micro-benchmarks/1350/ Results
|
Thanks @lpinca what do you think about the results? |
It seems we only have a benchmark for |
Hi! It's been a little while since this PR was last updated. Currently, it's in the squash queue, but not the commit queue. If you wish to pursue this further, I suggest verifying that it is still applicable/viable now, and having the team perform some reviews. Thank you!
@nodejs/assert |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should properly benchmark these changes. I'm requesting changes since this PR can land right now without it.
extracted from:
__proto__: null
in object #48646TODO:
reference: #48646 (comment)