WebAssembly / WebAssembly/threads
Why is buffer frozen?
Open
Nobody has claimed this yet.
- Dominant language
- WebAssembly
- Stars
- 767
- Forks
- 54
- PR merge metrics
- No merged PRs in 30d
Description
Let status be SetIntegrityLevel(buffer, "frozen").
What does this accomplish?
Note that freezing an ArrayBuffer does not prevent mutating its data:
const ab = new ArrayBuffer(20);
Object.freeze(ab);
const ta = new Uint8Array(ab);
ta[0] = 5; // works fine
So I'm not sure why you'd want to freeze the buffer. A note in the spec would be helpful explaining the purpose.
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 at the specification text for SetIntegrityLevel(buffer, "frozen") and review the surrounding ArrayBuffer and typed-array semantics. The issue is done when the specification includes a clear note explaining the purpose of freezing an ArrayBuffer despite its data remaining mutable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, wasm
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100