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.

Überprüfe die aufgeführten Operationen—sliceToImmutable, TypedArray write methods, SetViewValue, ArrayBufferCopyAndDetach und Atomics—und vergleiche ihre aktuelle Reihenfolge der Validierungen. Das Issue ist erst abgeschlossen, nachdem der Vorschlag klärt, wann Fehler aufgrund unveränderlicher Buffer im Verhältnis zu Argument-, Bounds-, Detachment- und Zero-Length-Prüfungen auftreten sollen.