Open
Bug 1670026
Opened 4 years ago
Updated 1 month ago
[META] Resizable and growable ArrayBuffers
Categories
(Core :: JavaScript Engine, enhancement, P3)
Core
JavaScript Engine
Tracking
()
NEW
People
(Reporter: yulia, Unassigned)
References
(Depends on 2 open bugs, Blocks 1 open bug, )
Details
(4 keywords, Whiteboard: [DocArea=JS])
Currently at stage 2
Summary from the proposal:
ArrayBuffers have enabled in-memory handling of binary data and have enjoyed great success. This proposal adds new expressivity with two new types, ResizableArrayBuffer and GrowableSharedArrayBuffer, that allow in-place growth and shrinking of buffers. The transfer method is also re-introduced here as a standard way to detach ArrayBuffers, perform zero-copy moves, and to "fix" ResizableArrayBuffer instances to ArrayBuffer instances.
Comment 1•4 years ago
|
||
I strongly desire that the work on this is either coordinated closely with bug 1392234, which is actually high priority and has been languishing for much too long, or is done after that bug, so as not to get in the way of it.
See Also: → 1392234
Reporter | ||
Updated•3 years ago
|
Reporter | ||
Updated•2 years ago
|
Summary: Implement Resizable and growable ArrayBuffers → [META] Resizable and growable ArrayBuffers
Updated•5 months ago
|
Updated•1 month ago
|
Keywords: parity-chrome,
parity-safari
You need to log in
before you can comment on or make changes to this bug.
Description
•