Re: [whatwg/webidl] Fix `BufferSource` algorithms for shared and resizable buffers (PR #1529)

@MattiasBuelens pushed 37 commits.

503621242c3df48ea75b145e438a786c63cc9c0a  Fix buffer source's byte length
970452d4ac18ec5fd59dd7c40404c900420fcea6  Add byte offset to ArrayBufferView
6b6381de82a474ea6ac86f7e5453c69fa3272ec1  Fix writing bytes into an ArrayBufferView backed by a SharedArrayBuffer
42f4781dcfcd18f267fbb0622cfc230d7a15f5da  Simplify writing into an ArrayBufferView
9837ea78a54060924aa009b2198831c36f3f256f  Move assert before conversion
e2f4a93678e0bc88353602fd4ff79c3c4d63e768  Use ArrayBufferCopyAndDetach to transfer an ArrayBuffer
e9ed7d637b7dfe7b8795bb24a53afbca939229a7  Rework "get a copy of the bytes held"
12f586fc34be2dc88fc778363167797863902ac0  Use IsArrayBufferViewOutOfBounds instead
c658d6994480f9180871eb09972f033578215273  Use SEQ-CST ordering to match ECMAScript
f0cf974b595cc2f5d86b1c42b2e94fc3e6e7c3e0  Use "then" only for checks with a single step
bf48fc19eec04c288ed3893707608e4cfe281c1d  Auto-link "assert"
c4b7e2e2e0af1a71b412d4685111c8dc40c48599  Check IsTypedArrayOutOfBounds
bad224821ad10319309bbe1855968bc93906d586  Use ArrayBufferByteLength for both ArrayBuffer and SharedArrayBuffer
c46a4be770e42d5e150c1fcd80b7427a0c00c630  Add a "then"
1d1c89475cdb3dec63fbd3ae96c5f0b89339868b  Make byte length throw if DataView is out of bounds
899c6a0d2cd271f0d22f8e2ac6d74605ee9c93ec  Check if detached before reading byte offset
28ae6668d1cff42095ad18f4d2c36417aeff49f8  Return immediately if length is 0
ade6c84ce3caf28260a90a0fc8bd0796e172725b  Reorder steps
dbdba4e5e89b802b7169d354b391cc9b4a20c047  Add "out of bounds" definition for ArrayBufferViews
946668edc7494278f2fc9acb97a9a1c95a49364f  Read byte offset before checking length
c0a4fa70fd8a97205eb495eab4a35f2677fbc6fc  Add notes for steps that mirror ECMAScript
fbf1b09aeb98061cf3dcafa971921b932b16694d  Remove TODO
11bddb9e6abc70546339cc64aec3be7dd18298fc  Define "out of bounds" before its call sites
4ac57f477219037445add0080346fe6df66445cb  Don't throw for out-of-bounds typed arrays in byte offset
1955091d79a3f45073b0b92201b4049d3314bcb3  Discriminate on [[DataView]] in byte length
6133e3f7474a59b8d649ec6a8b8b6120aea08b2d  Assert that view is in bounds before writing
92d6c07f6ec3df89c14d8d564863c5ebb695c187  Simplify ArrayBuffer/transfer
ab4a9307e560792c9a2f9cabbf33136a69c9d684  Fix dangling realm references in transfer note
0218fcbf089333f0812ec50af3689e2e3c111e26  Document when reading a byte length or copying bytes throws
fa429eb9aa6f6ebe507f9d9f9e6b70bb56ca1060  Use plain "Assert:" steps
5a8ef6653a993bef2a50b66f6f7ac562fa719a5d  Use scoped reference for BufferSource/byte length
ae01d9fe66af2e3bcf3793760dba81f151c45a29  Move and shorten note
939eb2d4a8d04732d43a5dffde77ac8d05d21a1b  Add newline
0c786ab43c1fdc5342bdd908a2ce281d2f249103  Remove note since step is *actually* necessary
36368464c7386b621f89a7da3e377ca695fcb8e2  Clarify that a detached buffer source never throws
2a364f1ffdbf897f43081f010b28702ba871e377  Revert "Remove note since step is *actually* necessary"
9a418e658cf1210a5936e702af3d4ae223bd5e98  Use "the exclusive range" in note

-- 
View it on GitHub:
https://github.com/whatwg/webidl/pull/1529/changes/3fff79f6fda50231daee3a33edf87422514110c5..9a418e658cf1210a5936e702af3d4ae223bd5e98
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/webidl/pull/1529/before/3fff79f6fda50231daee3a33edf87422514110c5/after/9>

Received on Monday, 31 August 2026 09:22:13 UTC