WebAssembly / WebAssembly/WASI
[v0.3] specify order for fields#get, fields#set
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 5.8k
- Forks
- 333
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 3
Description
For the operations on a fields resource that set or get all values of a named field, the specification should indicate their order; is it serialization order?
Also, what does it mean actually for a name to have multiple values? For HTTP/1.1, would that correspond to multiple Name: Value lines? That is my assumption but it might be good to spell it out somehow.
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 locating the specification sections for fields#get and fields#set. Determine and document the ordering of values, then clarify what multiple values for one name mean and whether HTTP/1.1 maps them to repeated header lines. Done means the specification answers both questions unambiguously.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- wasm
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100