array-iterator.js: use object_get_prototype_of instead of directly accessing the proto

array-iterator.js: use object_get_prototype_of instead of directly accessing the proto

Instead of directly looking up Uint8Array.__proto__, to get a hold of
the TypedArray prototype, use object_get_prototype_of. This is a
functionally equivalent, but cleaner approach.

Committed: https://crrev.com/04aa9436ce01c3a6b793d45f9741cb6ae67916a1
Cr-Commit-Position: refs/heads/master@{#36340}

[gsathya, 2016-05-18 19:18:54]

Description was changed from

==========
array-iterator.js: use object_get_prototype_of instead of directly accessing the
proto

Instead of directly looking up Uint8Array.__proto__, to get a hold of
the TypedArray prototype, use object_get_prototype_of. This is a
functionally equivalent, but cleaner approach.
==========

to

==========
array-iterator.js: use object_get_prototype_of instead of directly accessing the
proto

Instead of directly looking up Uint8Array.__proto__, to get a hold of
the TypedArray prototype, use object_get_prototype_of. This is a
functionally equivalent, but cleaner approach.
==========

[gsathya, 2016-05-18 19:18:54]

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

[gsathya, 2016-05-18 19:19:07]

The CQ bit was checked by gsathya@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-05-18 19:19:17]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1990983002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1990983002/1

[gsathya, 2016-05-18 19:23:09]

This got lost in the revert of the typedarray optimization fix.

[commit-bot: I haz the power, 2016-05-18 19:48:57]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-05-18 19:48:58]

Dry run: This issue passed the CQ dry run.

[Dan Ehrenberg, 2016-05-18 21:02:27]

The CQ bit was checked by littledan@chromium.org

[Dan Ehrenberg, 2016-05-18 21:02:28]

lgtm

[commit-bot: I haz the power, 2016-05-18 21:02:38]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1990983002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1990983002/1

[commit-bot: I haz the power, 2016-05-18 21:04:21]

Description was changed from

==========
array-iterator.js: use object_get_prototype_of instead of directly accessing the
proto

Instead of directly looking up Uint8Array.__proto__, to get a hold of
the TypedArray prototype, use object_get_prototype_of. This is a
functionally equivalent, but cleaner approach.
==========

to

==========
array-iterator.js: use object_get_prototype_of instead of directly accessing the
proto

Instead of directly looking up Uint8Array.__proto__, to get a hold of
the TypedArray prototype, use object_get_prototype_of. This is a
functionally equivalent, but cleaner approach.
==========

[commit-bot: I haz the power, 2016-05-18 21:04:22]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-05-18 21:04:38]

Description was changed from

==========
array-iterator.js: use object_get_prototype_of instead of directly accessing the
proto

Instead of directly looking up Uint8Array.__proto__, to get a hold of
the TypedArray prototype, use object_get_prototype_of. This is a
functionally equivalent, but cleaner approach.
==========

to

==========
array-iterator.js: use object_get_prototype_of instead of directly accessing the
proto

Instead of directly looking up Uint8Array.__proto__, to get a hold of
the TypedArray prototype, use object_get_prototype_of. This is a
functionally equivalent, but cleaner approach.

Committed: https://crrev.com/04aa9436ce01c3a6b793d45f9741cb6ae67916a1
Cr-Commit-Position: refs/heads/master@{#36340}
==========

[commit-bot: I haz the power, 2016-05-18 21:04:39]

Patchset 1 (id:??) landed as
https://crrev.com/04aa9436ce01c3a6b793d45f9741cb6ae67916a1
Cr-Commit-Position: refs/heads/master@{#36340}