Don't throw on assignment to function name binding in harmony sloppy mode

Don't throw on assignment to function name binding in harmony sloppy mode

BUG=v8:4482
LOG=n

Committed: https://crrev.com/18534dffc911ec9bd1285f1e9c2e14272e83097c
Cr-Commit-Position: refs/heads/master@{#31218}

[adamk, 2015-10-09 23:21:27]

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

[Dan Ehrenberg, 2015-10-09 23:44:18]

lgtm

[rossberg, 2015-10-12 08:55:46]

Just a note that we need a plan for this. We want to get rid of CONST_LEGACY
eventually, so this nay need to be substituted by a different (hopefully less
intrusive) mechanism.

[adamk, 2015-10-12 16:32:13]

On 2015/10/12 08:55:46, rossberg wrote:
> Just a note that we need a plan for this. We want to get rid of CONST_LEGACY
> eventually, so this nay need to be substituted by a different (hopefully less
> intrusive) mechanism.

Yep, we should be able to get away with something simpler than CONST_LEGACY to
get the right non-assignability semantics. But it doesn't seem worth doing that
refactoring until CONST_LEGACY is otherwise dead.

[adamk, 2015-10-12 16:32:18]

The CQ bit was checked by adamk@chromium.org

[commit-bot: I haz the power, 2015-10-12 16:32:25]

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

[commit-bot: I haz the power, 2015-10-12 16:55:27]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-10-12 16:55:47]

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