Skip to content

Conversation

KKiiim
Copy link

@KKiiim KKiiim commented Sep 17, 2025

  • 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

@KKiiim KKiiim changed the title feat: remove the active init operation of zero-initialized memory of makeFieldInitializationInConstructor feat: optimize the active init operation of zero-initialized memory of makeFieldInitializationInConstructor Sep 17, 2025
Copy link
Member

@HerrCai0907 HerrCai0907 left a 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.

@KKiiim
Copy link
Author

KKiiim commented Sep 25, 2025

@CountBleck Could you please have a look on this PR (^_^)

Copy link
Member

@CountBleck CountBleck left a 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.

@KKiiim KKiiim requested a review from CountBleck October 2, 2025 07:01
HerrCai0907 pushed a commit to wasm-ecosystem/warpo that referenced this pull request Oct 11, 2025
@KKiiim
Copy link
Author

KKiiim commented Oct 11, 2025

@coderabbitai summary

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants