Fix TypedArray Property optimizations

src/js/array-iterator.js

 // Copyright 2013 the V8 project authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 (function(global, utils) {
 
 "use strict";
 
 %CheckIsBootstrapping();
 
 // -----------------------------------------------------------------------
 // Imports
 
 var arrayIterationKindSymbol =
     utils.ImportNow("array_iteration_kind_symbol");
 var arrayIteratorNextIndexSymbol =
     utils.ImportNow("array_iterator_next_symbol");
 var arrayIteratorObjectSymbol =
     utils.ImportNow("array_iterator_object_symbol");
 var GlobalArray = global.Array;
 var IteratorPrototype = utils.ImportNow("IteratorPrototype");
 var iteratorSymbol = utils.ImportNow("iterator_symbol");
 var MakeTypeError;
 var toStringTagSymbol = utils.ImportNow("to_string_tag_symbol");
-var GlobalTypedArray = global.Uint8Array.__proto__;
+var GlobalTypedArray = %object_get_prototype_of(global.Uint8Array);

[adamk, 2016/05/06 17:56:12]

Did we ever figure out why this had to change? It still sounds worrying to me;
I'd suggest trying reverting this change and seeing if everything works.

[Dan Ehrenberg, 2016/05/06 18:09:33]

From off-line communication, sounds like it didn't have to change, and the old
way worked. However, I think this phrasing is cleaner--it depends on less, and
requires less thinking about the state of the world to prove that it's correct.

[adamk, 2016/05/06 18:11:31]

Sounds good, and I agree that this way of spelling it is clearer.

 
 utils.Import(function(from) {
   MakeTypeError = from.MakeTypeError;
 })
 
 // -----------------------------------------------------------------------
 
 function ArrayIterator() {}
 
 
@@ skipping 126 matching lines @@
 // -------------------------------------------------------------------
 // Exports
 
 utils.Export(function(to) {
   to.ArrayValues = ArrayValues;
 });
 
 %InstallToContext(["array_values_iterator", ArrayValues]);
 
 })