Seemingly inconsistent behavior in TypedArray constructor

[jugglinmike]

When constructing a TypedArray from an existing TypedArray whose underlying ArrayBuffer is out-of-bounds, an error is thrown only if the array being created is of a different type.

const resizableAb = new ArrayBuffer(100, {maxByteLength: 100});
const source = new Int8Array(resizableAb, 50);

resizableAb.resize(1);
// The `source` array is now out-of-bounds.

new Int8Array(source);  // creates an Int8Array of length 0
new Uint8Array(source); // throws a TypeError

I can see a rationale for either behavior, but I'm having trouble explaining why both should be observed based on the constructor. Is this intentional?

[syg]

Oh that's interesting, that's not intentional. The intent was to throw a TypeError in both cases.

[jugglinmike]

Thanks for confirming! Here's one way we might address it: gh-58