WebAssembly / WebAssembly/WASI
Forbid non-ascii field names
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 5.8k
- Forks
- 333
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 3
Description
Right now, the field-name production is a string which is specified to be compared case-insensitively with regards to equality. Case-insensitive comparisons are cheap to do for ASCII, but a bit annoying for full unicode. Fortunately (?), field names are always ASCII; values are not but that's OK. So, what about adding a restriction in wasi:http that forbids non-ascii field names?
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 reviewing the wasi:http field-name production and its case-insensitive equality requirement. Determine how the specification should state an ASCII-only restriction for field names while leaving values unrestricted, and treat an agreed specification change as done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- wasm
- Domain
- api, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100