demo · v136
Migration diff
The same buffer copy written two ways — pre-136 with the explicit offsets/size required, 136+ with the new short overload that copies the whole source buffer. Both paths are executed and their results compared so you can verify the new form has identical semantics.
Probing WebGPU adapter…
pre-136 (explicit)
encoder.copyBufferToBuffer( src, 0, dst, 0, src.size, );
136+ (short overload)
encoder.copyBufferToBuffer(src, dst);
pre-136 path—
136+ overload path—
bytes match?—
why this angle
The sibling concept demonstrates the overload's existence. This concept proves equivalence: same input, two API forms, byte-for-byte identical output buffers. It's the migration checklist a code reviewer would want.
see also
- copyBufferToBuffer overload — feature index
- Overload concept
- ChromeStatus entry
- WebGPU spec