-
-
Notifications
You must be signed in to change notification settings - Fork 677
feat: optimize the active init operation of zero-initialized memory of makeFieldInitializationInConstructor
#2948
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
base: main
Are you sure you want to change the base?
Conversation
makeFieldInitializationInConstructor
makeFieldInitializationInConstructor
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.
optimization goal LGTM. But I think we should only check whether the field is straightly initialized by zero and ignore it.
@CountBleck Could you please have a look on this PR (^_^) |
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.
This seems mostly okay, but I'm wondering what all the removed $~lib/arraybuffer/ArrayBufferView#set:buffer
is about...what is that setter function supposed to be doing anyway?
I'd like @MaxGraey to sign off before merging.
@coderabbitai summary |
Reduce unnecessary zero-initialization memory in the constructor
According to wasm-spec, grown memories should initialized with value 0x00
I've read the contributing guidelines
I've added my name and email to the NOTICE file