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

Handle _initialize non existence in wasi reactor modules #70

Merged
merged 1 commit into from
Mar 11, 2024

Conversation

TerrorJack
Copy link
Contributor

The _initialize export is optional and may not exist in a wasi reactor module, according to https://github.com/WebAssembly/WASI/blob/main/legacy/application-abi.md#current-unstable-abi. When it doesn't exist, simply don't do anything. This is especially useful in cases where a module has been pre-initialized by wizer and the _initialize export has been stripped.

The `_initialize` export is optional and may not exist in a wasi
reactor module, according to
https://github.com/WebAssembly/WASI/blob/main/legacy/application-abi.md#current-unstable-abi.
When it doesn't exist, simply don't do anything. This is especially
useful in cases where a module has been pre-initialized by `wizer` and
the `_initialize` export has been stripped.
@bjorn3
Copy link
Owner

bjorn3 commented Mar 11, 2024

Makes sense. Thanks!

@bjorn3 bjorn3 merged commit 6f7a996 into bjorn3:main Mar 11, 2024
1 check passed
@TerrorJack TerrorJack deleted the _initialize_optional branch March 11, 2024 11:06
@TerrorJack
Copy link
Contributor Author

Would you do a point release? It'll be helpful to downstream projects, thanks in advance :)

@bjorn3
Copy link
Owner

bjorn3 commented Mar 11, 2024

Done

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.

None yet

2 participants