Make array __proto__ manipulations not disturb the species protector

test/mjsunit/harmony/array-species-constructor.js

Index: test/mjsunit/harmony/array-species-constructor.js
diff --git a/test/mjsunit/harmony/array-species-constructor.js b/test/mjsunit/harmony/array-species-constructor.js
index d4eeefa010bd987ce960a982d3c2b3604049a266..d766e09eee058862527bb31b45c90a53be183099 100644
--- a/test/mjsunit/harmony/array-species-constructor.js
+++ b/test/mjsunit/harmony/array-species-constructor.js
@@ -2,7 +2,7 @@
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
-// Flags: --harmony-species
+// Flags: --harmony-species --allow-natives-syntax
 
 // Overwriting the constructor of an instance updates the protector
 
@@ -18,6 +18,7 @@ assertEquals(1, x.concat([1])[0]);
 class MyArray extends Array { }
 
 x.constructor = MyArray;
+assertFalse(%SpeciesProtector());

[Camillo Bruni, 2016/05/11 12:50:08]

nit: could you also check that the SpeciesProtector is valid before you change
the constructor?

[Dan Ehrenberg, 2016/05/11 14:32:16]

No because apparently 'stress' runs happen multiple times in the same isolate
and that fails.

 
 assertEquals(MyArray, x.map(()=>{}).constructor);
 assertEquals(MyArray, x.filter(()=>{}).constructor);