WebAssembly / WebAssembly/component-model
Kebab-case definition produces collision when mapped to snake_case
Open
Nobody has claimed this yet.
- Dominant language
- WebAssembly
- Stars
- 1.4k
- Forks
- 130
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 15
Description
The component-model grammar has this for <name>:
name ::= <word>
| <name>-<word>
word ::= [a-z][0-9a-z]*
| [A-Z][0-9A-Z]*
That accepts both "apple" and "APPLE". This leads to collisions when converting to snake_case for languages which use that convention.
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 the component-model grammar shown in the issue and trace how its name and word productions admit both casing forms. Review the five existing comments for prior decisions or constraints. Done means the specification resolves the casing ambiguity so valid names cannot collide after snake_case conversion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- wasm
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100