In %TypedArray%.from, use InternalArray rather than GlobalArray

In %TypedArray%.from, use InternalArray rather than GlobalArray

This patch holds intermediate results from %TypedArray%.from in an
InternalArray. The change should help TypedArray behavior not be
altered by changes to Array or Array.prototype. However, I can't
think of a test case where it's actually visible, so I haven't
added any tests in this patch.

BUG=v8:4128
R=adamk
LOG=y

[Dan Ehrenberg, 2015-06-11 17:18:10]

littledan@chromium.org changed reviewers:
+ littledan@chromium.org

[adamk, 2015-06-11 17:36:33]

Given what's going on in the other patch, this will be strictly slower, as
you'll miss the fast path for the Array constructor.

I don't think this is really worth it, since it has no effect on the behavior
(and we'll have tests already that Array.from doesn't look at the prototype of
the object it works on).

[arv (Not doing code reviews), 2015-06-11 17:39:40]

On 2015/06/11 17:36:33, adamk wrote:
> Given what's going on in the other patch, this will be strictly slower, as
> you'll miss the fast path for the Array constructor.
> 
> I don't think this is really worth it, since it has no effect on the behavior
> (and we'll have tests already that Array.from doesn't look at the prototype of
> the object it works on).

I agree. Sorry for causing extra work here.