WebAssembly / WebAssembly/custom-descriptors
Builtin proxy-like mechanism for importing empty prototypes
Nobody has claimed this yet.
- Dominant language
- WebAssembly
- Stars
- 12
- Forks
- 3
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 1
Description
#44 describes using a Proxy to import an arbitrary number of empty prototype objects with no code size overhead on the JS side. This seems to perform well enough in some initial tests on V8, but if there are performance concerns about using a Proxy like that, we could standardize some new API/mechanism to achieve the same end.
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 issue #44 and the initial V8 performance results referenced here. Establish whether the Proxy approach has unacceptable performance, then determine what a standardized mechanism for importing arbitrary empty prototype objects would need to provide; completion would require an agreed API or mechanism, not just another performance observation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, wasm
- Domain
- compilers, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100