introduce wasm_runtime_instantiate_ex2#4444
Merged
lum1n0us merged 2 commits intobytecodealliance:mainfrom Jul 14, 2025
Merged
Conversation
yamt
requested review from
TianlongLiang,
loganek,
lum1n0us,
no1wudi,
wenyongh and
xujuntwt95329
as code owners
yamt
force-pushed
the
wasm_runtime_instantiate_ex2
branch
from
1a2ee54 to
8f96cb1
Compare
yamt
commented
Jul 2, 2025
at this point, just a slightly inefficiant functionality equivalent of wasm_runtime_instantiate_ex. however, unlike wasm_runtime_instantiate_ex, this one is designed to be extendable without breaking the user-visible ABI. because the definition of InstantiationArgs2 is not exposed to users, we can safely add new members to it. this commit also makes wasm_runtime_instantiate_ex a wrapper of wasm_runtime_instantiate_ex2. if this goes well, maybe it's a good idea to apply a similar pattern to RuntimeInitArgs, LoadArgs, SharedHeapInitArgs, etc. i started with InstantiationArgs just because i happen to have a need to extend it for wasi-nn. cf. bytecodealliance#4364 bytecodealliance#4331
yamt
force-pushed
the
wasm_runtime_instantiate_ex2
branch
from
8f96cb1 to
392482c
Compare
lum1n0us
reviewed
Jul 10, 2025
Contributor
lum1n0us
left a comment
lum1n0us
left a comment
There was a problem hiding this comment.
IIUC, there should be some APIs related to WASI. OR are they included in another PR?
Contributor
Author
i plan to add them later. |
Contributor
Author
i meant another PR. |
lum1n0us
approved these changes
Jul 11, 2025
TianlongLiang
approved these changes
Jul 11, 2025
lum1n0us
added
breaking-change
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
at this point, just a slightly inefficiant functionality
equivalent of wasm_runtime_instantiate_ex.
however, unlike wasm_runtime_instantiate_ex, this one is designed
to be extendable without breaking the user-visible ABI.
because the definition of InstantiationArgs2 is not exposed to
users, we can safely add new members to it.
this commit also makes wasm_runtime_instantiate_ex a wrapper
of wasm_runtime_instantiate_ex2.
if this goes well, maybe it's a good idea to apply a similar
pattern to RuntimeInitArgs, LoadArgs, SharedHeapInitArgs, etc.
i started with InstantiationArgs just because i happen to have
a need to extend it for wasi-nn.
cf.
#4364
#4331