WebAssembly / WebAssembly/component-model
`overload` convention
Nobody has claimed this yet.
- Dominant language
- WebAssembly
- Stars
- 1.4k
- Forks
- 130
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 15
Description
Currently, each function has a different name.
Can we add #overload(target_name) to require languages that support overloading to generate an overloaded version of the function?
Different languages have different overload resolutions, so the selected function instances will be different.
This is an unsafe ffi operation, so it is just a overload suggestion.
The overload version is generated based on the original version.
In case of error resolution, the user can manually call the function of the original version.
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
No files, tests, or entry points are named. Start by reviewing the component-model specification and existing convention definitions, then determine where an overload annotation would be specified and how language-specific resolution and fallback to the original function should be documented; done requires an agreed design.
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