Inline SetLengthWithoutNormalize into its callers

Inline SetLengthWithoutNormalize into its callers

BUG=

Committed: https://crrev.com/7028e4b531f805ebb2555a7606f5a16cc14b02e5
Cr-Commit-Position: refs/heads/master@{#29165}

[Toon Verwaest, 2015-06-19 15:27:14]

verwaest@chromium.org changed reviewers:
+ jkummerow@chromium.org

[Toon Verwaest, 2015-06-19 15:27:14]

ptal

[Jakob Kummerow, 2015-06-19 16:44:00]

lgtm

[Toon Verwaest, 2015-06-19 17:01:50]

The CQ bit was checked by verwaest@chromium.org

[commit-bot: I haz the power, 2015-06-19 17:02:06]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1194943002/20001

[commit-bot: I haz the power, 2015-06-19 18:59:18]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2015-06-19 18:59:34]

Patchset 2 (id:??) landed as
https://crrev.com/7028e4b531f805ebb2555a7606f5a16cc14b02e5
Cr-Commit-Position: refs/heads/master@{#29165}

[brucedawson, 2015-06-22 17:12:35]

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

[brucedawson, 2015-06-22 17:12:36]

https://codereview.chromium.org/1194943002/diff/20001/src/elements.cc
File src/elements.cc (right):

https://codereview.chromium.org/1194943002/diff/20001/src/elements.cc#newcode...
src/elements.cc:1323: Isolate* isolate = array->GetIsolate();
This declaration of 'isolate' shadows a seemingly identical declaration in the
outer scope. I don't think this is a bug, but it is a minor inefficiency and it
does have the potential to be confusing, especially after subsequent
modifications to the code.

Consider removing this declaration and using just the outer-scope declaration?

[Toon Verwaest, 2015-06-22 18:34:50]

Will do so: https://codereview.chromium.org/1196533004