Add wasm ctor and dtor calls to non-main exports in core #481
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of the change
Adds calls to
__wasm_call_ctors
and__wasm_call_dtors
in Wizer init function andjavy.invoke
function injavy_core.wasm
.Why am I making this change?
These functions need to be called in non-main functions that are exported from Rust crates that are compiled to a Wasm bin for parts of the WASI context to be initialized properly. This isn't currently causing a problem but would block code that tries to read environment variables or use directory preopens from working properly.
Checklist
javy-cli
andjavy-core
do not require updating CHANGELOG files.