WebAssembly / WebAssembly/tool-conventions
Custom section name recommendations to avoid conflicts
Nobody has claimed this yet.
- Dominant language
- WebAssembly
- Stars
- 372
- Forks
- 75
- PR merge metrics
- No merged PRs in 30d
Description
Custom sections are identified by unstructured string names, which presents the possibility of conflicts between different tools. This repo helps the situation by acting as a pseudo-registry of some "publicly well-known" custom section names, but doesn't help with less-common or private tooling.
I'd like to suggest that this repo publish a recommendation for formatting custom section names to help avoid conflicts. One obvious source of inspiration might be vendor mime types (e.g. vnd.acme.whatever) but I'm less concerned about the exact format than the general idea.
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
Review the repository's existing registry of publicly well-known custom section names and its current convention documents. Compare vendor MIME-type-style naming with the conflict risks for private tooling, then document a recommendation once maintainers agree on the format. Done means the repository publishes an agreed custom-section naming convention.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- wasm
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100