Repository navigation
Versioning of interfaces (modules) #29
Description
I'm working on Ewasm which tries to bring WebAssembly to Ethereum. We are evaluating how we could use WASI (core) or other modules.
As part of the design process we have realised that versioning is an important feature to have: ewasm/design#121
I wonder how WASI plans to solve versioning of its interfaces. I see some potential options:
- Would it be similar to Dynamic detection of host functionality #12 having a function to query the version?
- A system similar to glibc where either the namespace or the name has a pre/postfix? (This is option a) in the linked issue).
- A custom section listing interface version (This is option b) in the linked issue).
- Adding versioning to the wasm import sections themselves.
Probably there are other/better proposals. Was there any previous discussion about this topic?
Activity
sbc100 commentedon Jun 6, 2019
IIUC this is what is being discussed in #2. Or am I missing something?
sunfishcode commentedon Feb 19, 2020
WASI now has versioning of interfaces, using a version number formatted within the module-name field of wasm imports. And the mechanism for querying interfaces is optional imports.
chore: add w3c license to repository (WebAssembly#29)
Add more content to the README.md. (WebAssembly#29)
Merge pull request WebAssembly#29 from guybedford/patch-1
Remove unused `errno` values, and document others. (WebAssembly#57)
Merge pull request WebAssembly#29 from lann/field-values-arent-strings
Add an `insecure` interface. (WebAssembly#29)