Regarding computed field writes #1065
-
I was looking at the generated bytecode for computed field writes and cant understand the need for the is_undefined_or_null check.
Why do we need to do toPropKey twice if the receiver object is ~(null or undefined)? or does this handle some other case? |
Beta Was this translation helpful? Give feedback.
Answered by
bnoordhuis
May 23, 2025
Replies: 1 comment
-
No particular reason, it's just a missed optimization opportunity. quickjs only does ultra-local bytecode optimizations. |
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
meetesh06
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No particular reason, it's just a missed optimization opportunity. quickjs only does ultra-local bytecode optimizations.