tc39 / tc39/proposal-immutable-arraybuffer
Web platform integration
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 38
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
There are various web specs which use SetValueInBuffer directly (via WebIDL). These need to be updated and WPT tests written.
Also, there are specs which do a defensive copy of the bytes in a view which can be avoided when the buffer is immutable. This technically is an as-if optimization, but it's probably worth updating the WebIDL and consuming specs to call this out anyway because otherwise people will not know to make this optimization.
See discussion in Matrix.
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 linked WebIDL SetValueInBuffer and get-buffer-source-copy definitions, then identify the consuming web specifications that use them. Write the requested WPT tests and update those specifications to address immutable buffers and the avoidable defensive copy; use the linked Matrix discussion for context.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- testing-qa, web-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100