Order of operations, when to throw or silently do nothing?

• Should sliceToImmutable with reversed start and end throw an exception even though slice with the same arguments would not?

• Should trying to write data in an immutable ArrayBuffer via a TypedArray element set throw, even though trying to write out-of-bounds or to a detached ArrayBuffer does not?

• Should TypedArray write methods (copyWithin, fill, reverse, set, etc.) throw when their backing ArrayBuffer is immutable but the targeted range is zero-length? If so, how early or late in the algorithm? The methods currently inspect arguments after ValidateTypedArray.

Similarly,

• How early or late in SetViewValue against an immutable ArrayBuffer should an exception be thrown? It currently inspects arguments before IsViewOutOfBounds.

• Likewise for abstract operations such as ArrayBufferCopyAndDetach (which currently checks IsSharedArrayBuffer, then newLength, then IsDetachedBuffer).

• And also for Atomics functions.

检查列出的操作——sliceToImmutable、TypedArray write methods、SetViewValue、ArrayBufferCopyAndDetach 和 Atomics——并比较它们当前的验证顺序。只有在提案解决了不可变缓冲区错误应相对于参数、边界、分离和零长度检查何时发生之后，该 issue 才算完成。