Re: [webrtc-insertable-streams] Additional space in the buffer (#6)

In raw-videoframe-land, the tendency seems to be to declare the input object immutable and create a new buffer for the output object, given that any transform has to read from the input and write to the output (two memory accesses) anyway.
The videoframe object has a destroy() operation that declares its backing store freed; I wonder if it's possible to declare a destroyAndTakeOverAndTransform() operation that creates a new frame while doing an in-place operation on the buffer.

Seems hard.

-- 
GitHub Notification of comment by alvestrand
Please view or discuss this issue at https://github.com/w3c/webrtc-insertable-streams/issues/6#issuecomment-735413880 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config