WebAssembly / WebAssembly/tool-conventions
Linking.md: How should the linker handle non-"env" imports
Nobody has claimed this yet.
- Dominant language
- WebAssembly
- Stars
- 372
- Forks
- 75
- PR merge metrics
- No merged PRs in 30d
Description
I've got a change out that adds initial support for imports from custom modules: https://reviews.llvm.org/D45796
However I think we should probably handle them a little differently going forward.
Perhaps only "env" (or "__extern" or whatever we call the default) imports should be added to
the symbol table. Maybe imports should be not be resolved at static link time at all?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with Linking.md and the linked review D45796 to understand the initial custom-module import support. Decide how non-"env" imports should be treated at static link time and whether they belong in the symbol table; the issue is done when the chosen behavior is established and reflected in the linking conventions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- wasm
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100