WebAssembly / WebAssembly/WASI
Compatible with JS String Builtin proposal
Open
Nobody has claimed this yet.
S-inactive
- Dominant language
- Rust
- Stars
- 5.8k
- Forks
- 333
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 3
Description
The JS String Builtin provides a set of functions to the wasm:js-string namespace, and it is best to wit them to fit into the component model system.
- Standardize unmanaged core module imports in the
wasm:js-stringnamespace - Host can selectively implement some js functions
- Linker can select the required shim implementation
- As a shared core definition, other js binding libraries can import and pass js strings without loss
There are many details to discuss, such as
-
wasm:js-stringis not a valid world name - Is
js-stringa resource?
Contributor guide
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 by reading the linked JS String Builtin proposal, especially the wasm:js-string API, and compare it with the component model. The issue's open questions about the namespace, resource modeling, selective host support, linker shims, and shared core definitions must be resolved before the compatibility work can be considered complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, wasm
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100